Stored script execution via insufficient output escaping
Published Feb 25, 2025 · Updated Apr 28, 2026
Stored cross-site scripting in WPSoul Greenshift 10.8 and earlier allows remote authenticated users to inject scripts into WordPress pages. The page-rendering path stores contributor-supplied content and emits it without sufficient sanitization or output escaping, so embedded script reaches visitors’ browsers. Contributor-level access is required, and execution occurs when another user views the injected page.
Summary
What happened
Stored cross-site scripting in WPSoul Greenshift 10.8 and earlier allows remote authenticated users to inject scripts into WordPress pages. The page-rendering path stores contributor-supplied content and emits it without sufficient sanitization or output escaping, so embedded script reaches visitors’ browsers. Contributor-level access is required, and execution occurs when another user views the injected page.
The record
- CVE
- CVE-2025-26884
- Published
- Feb 25, 2025
- Updated
- Apr 28, 2026
- Vendor
- WPSoul
- Product
- Greenshift
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 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 <=10.8 changes=[{"at":"10.9","status":"unaffected"}]
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