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

> Attackers can trick logged-in admins into sending debug information to arbitrary email addresses via CSRF, exposing sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2023
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-q4v4-hpcx-wf3x

## What is CVE-2023-1623?

CVE-2023-1623 is a medium-severity vulnerability in Unknown Custom Post Type UI, published on 24 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

## Which versions are affected by CVE-2023-1623?

It affects 1 product.


Products: Webdevstudios Custom Post Type Ui.

## How do I fix CVE-2023-1623?

No fix has been published for CVE-2023-1623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-1623 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1623 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1623 and fix it if it is affected.

What it is: CVE-2023-1623 is a medium-severity vulnerability in Unknown Custom Post Type UI, published on 24 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1623 exists.

Affected product: Unknown Custom Post Type UI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1623/ (Markdown: https://insights.sbomify.com/CVE-2023-1623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1623
- OSV: https://osv.dev/vulnerability/CVE-2023-1623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1623/
Summaries are generated and may contain mistakes; the official description above is the record.