Stored XSS via forged privileged-user request
Published Jan 16, 2025 · Updated May 11, 2026
Cross-site request forgery in Shibu Lijack CJ Custom Content 2.0 and earlier allows remote attackers to store script in WordPress. Public records do not identify the request handler or field that accepts the forged update and persists unsanitized script content. Exploitation requires an authenticated privileged user to visit or submit attacker-controlled content, after which the stored script executes for site users.
Summary
What happened
Cross-site request forgery in Shibu Lijack CJ Custom Content 2.0 and earlier allows remote attackers to store script in WordPress. Public records do not identify the request handler or field that accepts the forged update and persists unsanitized script content. Exploitation requires an authenticated privileged user to visit or submit attacker-controlled content, after which the stored script executes for site users.
The record
- CVE
- CVE-2025-23869
- Published
- Jan 16, 2025
- Updated
- May 11, 2026
- Vendor
- Shibu Lijack
- Product
- CJ Custom Content
- Classifications
- CWE-352, CAPEC-592, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.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