PatchTheCVECVE-2023-1623: The Custom Post Type UI WordPress plugin before 1.13.5 does not properly check for CSRF when sending the debug
CVE-2023-1623 is a medium-severity flaw (CVSS 6.5) affecting custom post type ui. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Custom Post Type UI WordPress plugin before 1.13.5 does not properly check for CSRF when sending the debug information to a user supplied email, which could allow attackers to make a logged in admin send such information to an arbitrary email address via a CSRF attack.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.4% (top 71%) |
| CISA exploited list | No |
| Published | 2023-04-24 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-1623?
custom post type ui: upgrade to 1.13.5. Exact commands for each OS are on this page.
Is CVE-2023-1623 being exploited?
CVE-2023-1623 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-1623 affect?
CVE-2023-1623 affects custom post type ui. Severity is medium (CVSS 6.5). The Custom Post Type UI WordPress plugin before 1.13.5 does not properly check for CSRF when sending the debug information to a user supplied email, which could allow attackers to make a logged in admin send such information to an arbitrary
How urgent is CVE-2023-1623?
Priority 35/100. Public exploit reference