Stored XSS via unescaped after shortcode parameter
Published Feb 11, 2025 · Updated Apr 8, 2026
Stored XSS in the SuperSaaS WordPress plugin 2.1.12 and earlier allows remote authenticated users to inject scripts via the after parameter. The shortcode renderer places the after attribute into generated page output without sufficient input sanitization or context-appropriate escaping. Contributor-level access or higher is required; the stored script runs when an affected page is opened in a Chromium-based browser, allowing arbitrary script actions in that visitor's page context.
Summary
What happened
Stored XSS in the SuperSaaS WordPress plugin 2.1.12 and earlier allows remote authenticated users to inject scripts via the after parameter. The shortcode renderer places the after attribute into generated page output without sufficient input sanitization or context-appropriate escaping. Contributor-level access or higher is required; the stored script runs when an affected page is opened in a Chromium-based browser, allowing arbitrary script actions in that visitor's page context.
The record
- CVE
- CVE-2025-0862
- Published
- Feb 11, 2025
- Updated
- Apr 8, 2026
- Vendor
- SuperSaaS
- Product
- SuperSaaS
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 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 <=2.1.12
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