CVE-2023-6390 — The WordPress Users WordPress plugin through 1
The WordPress Users WordPress plugin through 1.4 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.
Published
2024-01-29T14:44:29.371Z
Last modified
2025-06-20T19:44:08.525Z
01What is this vulnerability?
The WordPress Users WordPress plugin through 1.4 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.
02Affected products
| Vendor | Product | Versions |
|---|
| Unknown | WordPress Users | 0 |
03Active exploitation status
Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.
04Recommended remediation
- Patch to a fixed version listed in the vendor advisory (see references below).
- Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
- Hunt historical logs for exploitation indicators — see Detection signatures below.
05Technical details
For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.
06Detection signatures
Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.
07Related CVEs
No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.
08Timeline
- Published: 2024-01-29T14:44:29.371Z
- Last modified: 2025-06-20T19:44:08.525Z
09References
- wpscan.com — https://wpscan.com/vulnerability/a0ca68d3-f885-46c9-9f6b-b77ad387d25d/
- magos-securitas.com — https://magos-securitas.com/txt/2023-6390.txt
Want this in your SOAR or SIEM?
SARA's API returns EPSS, CVSS, KEV, and an analyst-grade summary in one call.
Read the API reference →