Stored DOM XSS via insufficient output escaping
Published Jan 15, 2025 · Updated Apr 28, 2026
Stored DOM-based XSS in falldeaf WP ViewSTL 1.0 and earlier allows remote authenticated users to execute scripts in another user's browser. The rendering path fails to sanitize untrusted input and escape it before page output, but published sources do not identify the affected function or input. Contributor-level access and a victim viewing the injected page are required, limiting actions and data access to that user's browser context.
Summary
What happened
Stored DOM-based XSS in falldeaf WP ViewSTL 1.0 and earlier allows remote authenticated users to execute scripts in another user's browser. The rendering path fails to sanitize untrusted input and escape it before page output, but published sources do not identify the affected function or input. Contributor-level access and a victim viewing the injected page are required, limiting actions and data access to that user's browser context.
The record
- CVE
- CVE-2025-22742
- Published
- Jan 15, 2025
- Updated
- Apr 28, 2026
- Vendor
- falldeaf
- Product
- WP ViewSTL
- Classifications
- CWE-79, CAPEC-588, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 15, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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 <=1.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
No public exploit references are available in this record.
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