CVE-2023-6391: Custom User CSS (WordPress plugin) · Cross-Site Request Forgery (CSRF)
Affects Custom User CSS (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Unknown Custom User CSS | Affected
| Fixed in– |
AI-suggested
Immediate mitigation steps include disabling or uninstalling the Custom User CSS plugin until a patch is available. Administrators should audit their WordPress installations to identify the presence of this plugin and verify the version. If the plugin is essential, restrict administrative access to trusted users only and implement network-level protections such as Web Application Firewalls (WAFs) that can detect and block CSRF attack patterns. Educate administrators about the risks of clicking on untrusted links or visiting suspicious websites while logged into admin accounts. Monitoring for unexpected changes in plugin settings or CSS files can help detect exploitation attempts. Once a patch is released, apply it promptly. Additionally, implementing Content Security Policy (CSP) headers can help mitigate the impact of malicious CSS injection. Regular backups and incident response plans should be in place to recover from potential compromises.
Description
The Custom User CSS WordPress plugin through 0.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack.