Site defacement via unverified settings update
Published Jan 29, 2024 · Updated May 29, 2025
Cross-site request forgery in Custom User CSS 0.2 and earlier allows remote attackers to overwrite site CSS via a forged admin request. The settings handler accepts an action=update POST containing custom_user_css_css and writes the supplied CSS without validating a CSRF token. A logged-in administrator must open an attacker-controlled page that submits the form; the demonstrated consequence is site defacement through replaced CSS.
Summary
What happened
Cross-site request forgery in Custom User CSS 0.2 and earlier allows remote attackers to overwrite site CSS via a forged admin request. The settings handler accepts an action=update POST containing custom_user_css_css and writes the supplied CSS without validating a CSRF token. A logged-in administrator must open an attacker-controlled page that submits the form; the demonstrated consequence is site defacement through replaced CSS.
The record
- CVE
- CVE-2023-6391
- Published
- Jan 29, 2024
- Updated
- May 29, 2025
- Vendor
- Jeremiah Orem
- Product
- Custom User CSS
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2024CVE publishedPublication date reported by the CVE source.
- May 29, 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=0 <=0.2
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.
Public exploit references
- Forged settings form proof of conceptproof of concept · validated
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