dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13405

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Ace Post Type Builder WordPress plugin (versions up to 1.9) has a missing authorization vulnerability in the cptb_delete_custom_taxonomy() function. This function lacks proper capability checks, allowing any authenticated user with Subscriber-level access or higher to delete arbitrary custom taxonomies stored in the WordPress database.

MitigationUpdate to version 1.9.1 or later which includes proper authorization checks. If unable to update immediately, restrict user role assignments to prevent Subscriber-level access or disable the plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ace Post Type Builder plugin is installed
    Check if the plugin exists in the WordPress plugins directory (wp-content/plugins/ace-post-type-builder/) or view it in WP Admin under Plugins
    Affected if Plugin is present and active in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (ace-post-type-builder.php) and locate the Version header comment, or check the plugin row in WP Admin Plugins page
    Affected if Version is 1.9 or earlier (versions 1.9.1 and later contain the fix)
  3. Verify user role configuration
    Navigate to WordPress Users > Users List and review which users have the Subscriber role or higher, or check Users > User Roles if a role management tool is available
    Affected if Any user account with Subscriber-level access or higher exists in the system
  4. Confirm the vulnerable endpoint is accessible
    Test access to the taxonomy deletion functionality via the WordPress admin AJAX endpoint (wp-admin/admin-ajax.php with action=cptb_delete_custom_taxonomy) or inspect the plugin code for the cptb_delete_custom_taxonomy function
    Affected if The function is callable without elevated capability checks (any logged-in user with Subscriber role can trigger it)

A user is affected if the Ace Post Type Builder plugin version 1.9 or earlier is installed and active, and any Subscriber-level or higher user account exists in the WordPress environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.9.1 or later which includes proper authorization checks. If unable to update immediately, restrict user role assignments to prevent Subscriber-level access or disable the plugin until patched.

Recommended fix Moderate confidence

Ace Post Type Builder version 1.9.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Ace Post Type Builder plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is running version 1.9.1 or higher
  7. 7. Confirm that custom taxonomies can still be managed properly through the plugin interface

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13405 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data