dbcve.org
BookpressWordPress extension · Blackandwhitedigital

CVE-2025-25167

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-07
Fix available
A fix is available. Upgrade to after 1.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Black and White BookPress – For Book Authors book-press allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects BookPress – For Book Authors: from n/a through <= 1.2.7.

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 · moderate confidence

A missing authorization vulnerability in the BookPress – For Book Authors WordPress plugin (versions up to 1.2.7) allows unauthenticated attackers to access functionality that should require proper access control checks. The plugin fails to enforce authorization requirements on certain actions, enabling exploitation of incorrectly configured security levels.

MitigationApply the vendor patch or update to the latest version of BookPress – For Book Authors. If no patch is available, manually audit the plugin code to identify and add proper capability checks (current_user_can()) and nonce verification to all AJAX and admin actions.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BookpressWordPress extension
Affected:<= 1.2.7

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
High
Integrity
High
Availability
High

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

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 BookPress plugin is installed
    Navigate to the WordPress admin dashboard under Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'bookpress' or similar.
    Affected if The BookPress plugin by Blackandwhitedigital appears in the installed plugins list.
  2. Identify the installed version
    In the WordPress admin, view the plugin details to see the version number, or open the plugin's main PHP file (often in wp-content/plugins/bookpress/) and check the 'Version' header in the file comments.
    Affected if The version listed is 1.2.7 or lower.
  3. Verify administrative interface accessibility
    Attempt to access common BookPress admin endpoints (such as /wp-admin/admin.php?page=bookpress or similar paths) without authentication or with a low-privilege account.
    Affected if The administrative interfaces load or respond without requiring proper authentication or authorization validation.
  4. Check for server-level access restrictions
    Review web server configuration (e.g., .htaccess, nginx config) or hosting panel settings for any IP-based or password-based restrictions on the plugin's admin paths.
    Affected if No server-level access controls are configured to restrict access to the plugin's administrative functions.
  5. Inspect plugin capability checks
    Examine the plugin's PHP files for function calls that verify user capabilities or roles (such as current_user_can()) before performing administrative actions.
    Affected if The plugin lacks or incorrectly implements capability checks before allowing access to book data management functions.

The environment is affected if BookPress plugin version 1.2.7 or lower is installed AND the plugin's administrative interfaces are accessible without proper authorization controls.

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
Upgrade available Upgrade to a release after 1.2.7
Interim mitigation

Apply the vendor patch or update to the latest version of BookPress – For Book Authors. If no patch is available, manually audit the plugin code to identify and add proper capability checks (current_user_can()) and nonce verification to all AJAX and admin actions.

Fix this in Bookpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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