Stored XSS via unescaped class_name attribute
Published Jun 27, 2025 · Updated Apr 8, 2026
Stored XSS in OsomPress Osom Blocks 1.2.1 and earlier allows remote authenticated users to inject scripts through class_name. The CPT-list block renderer writes the stored class_name value into generated HTML without adequate input sanitization or output escaping. Contributor-level access is sufficient to plant the payload, which executes in another user's browser whenever the affected page is viewed.
Summary
What happened
Stored XSS in OsomPress Osom Blocks 1.2.1 and earlier allows remote authenticated users to inject scripts through class_name. The CPT-list block renderer writes the stored class_name value into generated HTML without adequate input sanitization or output escaping. Contributor-level access is sufficient to plant the payload, which executes in another user's browser whenever the affected page is viewed.
The record
- CVE
- CVE-2025-5940
- Published
- Jun 27, 2025
- Updated
- Apr 8, 2026
- Vendor
- OsomPress
- Product
- Osom Blocks
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 27, 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 <=1.2.1
What conditions does exploitation require?
What is affected?
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