dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-12126

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 The Total Book Project plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.0 via several functions due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to perform several actions like moving/deleting/creating chapters in books that do not belong to them.

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 Total Book Project WordPress plugin versions up to 1.0 contains an Insecure Direct Object Reference vulnerability where multiple functions accept user-controlled keys without proper validation. Authenticated users with Contributor-level permissions can manipulate chapter operations (move, delete, create) on books they do not own by exploiting the lack of ownership verification on the book/chapter identifiers.

MitigationImplement proper authorization checks and ownership validation on all book/chapter manipulation functions to ensure users can only modify resources they own. Require explicit capability checks and validate that the requested book ID belongs to the authenticated user before allowing any operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 plugin installation
    Navigate to WordPress admin > Plugins and look for 'Total Book Project' in the installed plugins list, or inspect the wp-content/plugins/ directory for a folder named 'total-book-project' or similar.
    Affected if The plugin is installed and active.
  2. Identify plugin version
    Open the main plugin file (usually total-book-project.php or similar in wp-content/plugins/) and look for the 'Version' header comment, or check the plugin's readme.txt file.
    Affected if The installed version is 1.0 or lower.
  3. Verify Contributor role exists
    Go to WordPress admin > Users > Roles, or use a role management plugin, or query the wp_options table for the wp_user_roles option to confirm Contributor role is active.
    Affected if Contributor role is enabled and users with this role exist.
  4. Check book ownership validation in plugin code
    Examine the plugin PHP files (particularly those handling chapter operations like move, delete, create) for missing checks on book/chapter ownership. Look for functions that accept book_id or chapter_id parameters without verifying the current user owns the associated book.
    Affected if The plugin code lacks ownership/authorization checks before allowing book or chapter operations.
  5. Test if cross-user book manipulation is possible
    Using a Contributor-level user account, attempt to access or modify a book created by a different user by manipulating book/chapter IDs in API requests or plugin functions.
    Affected if A Contributor can manipulate books or chapters they do not own.

A user is affected if the Total Book Project plugin version 1.0 or lower is installed, the Contributor role is active, and the plugin lacks proper ownership validation on book/chapter manipulation functions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks and ownership validation on all book/chapter manipulation functions to ensure users can only modify resources they own. Require explicit capability checks and validate that the requested book ID belongs to the authenticated user before allowing any operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12126 — 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-12126 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