CVE-2025-31896
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 · uneditedMissing Authorization vulnerability in istmoplugins GetBookingsWP get-bookings-wp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GetBookingsWP: from n/a through <= 1.1.27.
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 confidenceThe GetBookingsWP WordPress plugin <= 1.1.27 contains a missing authorization vulnerability in the get-bookings-wp function. The plugin fails to properly verify user permissions before allowing access to booking data, allowing attackers with low-privilege access (such as subscriber-level users) or potentially unauthenticated attackers to read booking information they should not have access to.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify GetBookingsWP plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for GetBookingsWP. Note the version number displayed below the plugin name.Affected if The plugin is present in the WordPress installation.
-
Check the installed version against affected rangeCompare the installed version number to the affected range. The vulnerability affects versions 1.1.27 and below.Affected if Installed version is 1.1.27 or any earlier version.
-
Identify the vulnerable endpointLocate the get-bookings-wp AJAX handler or direct function call in the plugin files (typically in the main plugin PHP file or includes/ajax*.php). The vulnerable function is named get-bookings-wp.Affected if The get-bookings-wp function exists in the plugin code.
-
Test endpoint accessibility with low-privilege accountCreate or use a WordPress user with subscriber-level role. Attempt to access the get-bookings-wp endpoint (via AJAX at wp-admin/admin-ajax.php?action=get-bookings-wp or similar) using that account. Capture and inspect the response.Affected if The endpoint returns booking data to a subscriber-level user without requiring higher privileges.
-
Test unauthenticated accessMake a request to the get-bookings-wp endpoint without providing any authentication credentials (not logged in). Capture and inspect the response.Affected if The endpoint returns booking data to unauthenticated requests.
You are affected if GetBookingsWP version 1.1.27 or lower is installed AND the get-bookings-wp endpoint is accessible to subscriber-level users or unauthenticated attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade GetBookingsWP to the latest version which includes proper authorization checks. If no update is available, restrict access to the affected endpoint via server-side configuration or temporarily disable the plugin until a patch is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31896 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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