2026-10-17 21:56 CEST · Intelligence refreshed (Europe/Stockholm)
Understand software risk, with the evidence visible.
Search software, operating systems, packages, CVEs, KBs, campaigns, advisories, named operations or GHSAs and review correlated vulnerability, campaign, advisory, exploitation, update, affected-product and lifecycle intelligence in one place.
Latest synchronized CVE
CVSS 4.3Published 2026-10-17 21:00 CEST
Vendor
Affected products
1 affected products/devices1 software
General vulnerability queryRecent High & critical CVEs
Query the vulnerability time window. Default 7 days; narrow to the last 24 hours or expand to 14 or 30 days when needed.
CVSS 9.8/10Critical severity
First published: 16 October 2026, 19:39 CEST · Last modified: 16 October 2026, 23:19 CEST
CVE lookup — correlated security and lifecycle intelligence
· 7 sources correlated
Critical severity — prioritize remediation
Webreaper Damselfly through 4.5.3 Missing Authentication on REST API Controllers
SeverityCVSS 9.8Critical · Remote / network
ExploitationNone reportedEPSS 0.4% chance in 30 days
Webreaper Damselfly through 4.5.3 contains an authentication bypass vulnerability that allows unauthenticated attackers to access all /api/* routes because controller authorization attributes are commented out. Attackers can send PUT /api/users with Admin roles to create administrator accounts, or POST /api/users to reset any user's password, gaining full control.
Detailed evidence Everything below supports the summary above. Open only what you need.
Matched intelligence coverage 7 sources
EUVDGHSAOSVEPSSCWECVEAffected Products
Cross-source correlations 7 matched lanes
Direct intelligence-source relationships
Direct intelligence-source lanes: every lane below has direct evidence for
in that Scantide intelligence collection. Lanes share the CVE as their join key; their presence together does not imply that one source explicitly referenced another source's record.
These vendors are derived from affected product/device evidence tied to this CVE. This is intentionally separate from the direct intelligence-source lanes above: a vendor can have affected products without Scantide having a vendor-specific advisory or Microsoft KB record for the CVE.
1 affected vendors represented
Affected software, operating systems, hardware and devices 3
Deduplicated across Scantide's structured CVE, NVD applicability, CSAF, vendor advisory, campaign and downstream product evidence. Taxonomy IDs and evidence-only identifiers are excluded from the asset count. Counts represent relationships Scantide can currently prove, not the theoretical maximum downstream ecosystem.
Webreaper Damselfly through 4.5.3 contains an authentication bypass vulnerability that allows unauthenticated attackers to access all /api/* routes because controller authorization attributes are commented out. Attackers can send PUT /api/users with Admin roles to create administrator accounts, or POST /api/users to reset any user's password, gaining full control.
Webreaper Damselfly through 4.5.3 contains an authentication bypass vulnerability that allows unauthenticated attackers to access all /api/* routes because controller authorization attributes are commented out. Attackers can send PUT /api/users with Admin roles to create administrator accounts, or POST /api/users to reset any user's password, gaining full control.
Only sources that directly identify or describe the queried CVE are shown here. Historical examples from MITRE CWE definitions are kept in the weakness section and are not presented as related CVEs.
Affected-product scope: The product/device count is the deduplicated set Scantide can prove from its currently ingested structured records and advisory text. It is not a claim that only those products were affected; component vulnerabilities such as Log4Shell can have a much larger downstream ecosystem. Advisory and vendor references are kept clickable so additional downstream exposure can be followed to the authoritative source.
Coverage note: Scantide correlates multiple public and locally indexed intelligence sources, but no dataset or matching process is complete. Results may omit software, dependencies, affected versions or advisories, and related records do not by themselves prove that a specific installation is vulnerable. Confirm important findings against vendor guidance and the installed product and version.