Stored XSS via unescaped correlation titles
Published Aug 18, 2026 · Updated Aug 19, 2026
Stored XSS in correlation handling in SpiderFoot 4.0 and earlier allows attackers to execute script in an operator browser via crafted scan data. The correlation engine's build_correlation_title() function substitutes raw event values into rule headlines, scancorrelations() returns the title unchanged, and scaninfo.tmpl concatenates that value into an HTML string passed to jQuery .append(). Reachability requires control of data that SpiderFoot scans, such as a server banner, WHOIS field, bucket name, or document metadata; when an operator opens the Correlations tab, attacker JavaScript runs in that session and can read plaintext API keys from Settings and drive the UI.
Summary
What happened
Stored XSS in correlation handling in SpiderFoot 4.0 and earlier allows attackers to execute script in an operator browser via crafted scan data. The correlation engine's build_correlation_title() function substitutes raw event values into rule headlines, scancorrelations() returns the title unchanged, and scaninfo.tmpl concatenates that value into an HTML string passed to jQuery .append(). Reachability requires control of data that SpiderFoot scans, such as a server banner, WHOIS field, bucket name, or document metadata; when an operator opens the Correlations tab, attacker JavaScript runs in that session and can read plaintext API keys from Settings and drive the UI.
The record
- CVE
- CVE-2026-75626
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Steve Micallef
- Product
- SpiderFoot
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue #2012 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo