Stored XSS via unsanitized editor CSS injection
Published Dec 31, 2025 · Updated Dec 31, 2025
Stored XSS in Responsive Block Control 1.2.9 and earlier allows remote authenticated users to run script in an editor user's browser. The plugin's editor JavaScript injects a contributor-controlled customCss value into the page without adequate sanitization. Contributor access is required, and execution occurs when another user opens the affected block in the WordPress editor.
Summary
What happened
Stored XSS in Responsive Block Control 1.2.9 and earlier allows remote authenticated users to run script in an editor user's browser. The plugin's editor JavaScript injects a contributor-controlled customCss value into the page without adequate sanitization. Contributor access is required, and execution occurs when another user opens the affected block in the WordPress editor.
The record
- CVE
- CVE-2025-62135
- Published
- Dec 31, 2025
- Updated
- Dec 31, 2025
- Vendor
- Sascha Paukner
- Product
- Responsive Block Control
- Classifications
- CWE-79, CAPEC-588, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 31, 2025CVE publishedPublication date reported by the CVE source.
- Dec 31, 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=n/a <=1.2.9
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