Contributor-level stored XSS via insufficient input sanitization
Published Jan 23, 2026 · Updated Jan 23, 2026
Stored XSS in COP UX Flat 5.4.0 and earlier allows remote authenticated users to inject scripts into WordPress pages. Published records identify insufficient input sanitization and output escaping but do not name the affected field, function, or rendering path. Contributor-level access is required; injected scripts persist in pages and execute when those pages are accessed, exposing viewers' browser context to script actions.
Summary
What happened
Stored XSS in COP UX Flat 5.4.0 and earlier allows remote authenticated users to inject scripts into WordPress pages. Published records identify insufficient input sanitization and output escaping but do not name the affected field, function, or rendering path. Contributor-level access is required; injected scripts persist in pages and execute when those pages are accessed, exposing viewers' browser context to script actions.
The record
- CVE
- CVE-2026-24576
- Published
- Jan 23, 2026
- Updated
- Jan 23, 2026
- Vendor
- COP
- Product
- UX Flat
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2026CVE publishedPublication date reported by the CVE source.
- Jan 23, 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=n/a <=<= 5.4.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