# CVE-2025-12826: Missing authorization in Custom Post Type UI

> Authenticated subscribers can modify custom post types due to missing capability checks in the Custom Post Type UI plugin.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-p4vc-pp2h-cfvh

## What is CVE-2025-12826?

CVE-2025-12826 is a medium-severity missing authorization vulnerability in webdevstudios Custom Post Type UI, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Custom Post Type UI plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.18.0. This is due to the plugin not verifying that a user has the required capability to perform actions in the "cptui_process_post_type" function. This makes it possible for authenticated attackers, with subscriber level access and above, to add, edit, or delete custom post types in limited situations.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-12826?


## How do I fix CVE-2025-12826?

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

## Is CVE-2025-12826 being exploited?

There is no known exploitation of CVE-2025-12826 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12826 and fix it if it is affected.

What it is: CVE-2025-12826 is a medium-severity missing authorization vulnerability in webdevstudios Custom Post Type UI, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12826 in the wild and no public exploit code.

Affected product: webdevstudios 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-2025-12826/ (Markdown: https://insights.sbomify.com/CVE-2025-12826/index.md)
```

## Sources

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

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