# CVE-2025-13405: Missing authorization in Ace Post Type Builder

> Authenticated subscribers can delete arbitrary custom taxonomies due to missing authorization checks in the Ace Post Type Builder plugin.

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

## What is CVE-2025-13405?

CVE-2025-13405 is a medium-severity missing authorization vulnerability in buywptemplates Ace Post Type Builder, published on 25 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ace Post Type Builder plugin for WordPress is vulnerable to unauthorized custom taxonomy deletion due to missing authorization validation on the cptb_delete_custom_taxonomy() function in all versions up to, and including, 1.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary custom taxonomies.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-13405 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13405 is a medium-severity missing authorization vulnerability in buywptemplates Ace Post Type Builder, published on 25 Nov 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-13405 in the wild and no public exploit code.

Affected product: buywptemplates Ace Post Type Builder. 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-13405/ (Markdown: https://insights.sbomify.com/CVE-2025-13405/index.md)
```

## Sources

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

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