Stored XSS via unescaped FAQ CSS class
Published Aug 14, 2025 · Updated Aug 14, 2025
Stored XSS in Structured Content (JSON-LD) #wpsc before 1.7.0 allows remote authenticated users to execute script through an FAQ block. The FAQ block writes its Additional CSS class option into an HTML class attribute without validation or output escaping. Contributor access is sufficient to save the payload, but execution requires a user to preview or view the affected post and interact with its FAQ element.
Summary
What happened
Stored XSS in Structured Content (JSON-LD) #wpsc before 1.7.0 allows remote authenticated users to execute script through an FAQ block. The FAQ block writes its Additional CSS class option into an HTML class attribute without validation or output escaping. Contributor access is sufficient to save the payload, but execution requires a user to preview or view the affected post and interact with its FAQ element.
The record
- CVE
- CVE-2025-3414
- Published
- Aug 14, 2025
- Updated
- Aug 14, 2025
- Vendor
- Gordon Böhme, Antonio Leutsch
- Product
- Structured Content (JSON-LD) #wpsc
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2025CVE publishedPublication date reported by the CVE source.
- Aug 14, 2025Record 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 <1.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- FAQ Additional CSS class proof of conceptproof of concept · validated
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