dbcve.org
BookingpressWordPress extension · Reputeinfosystems

CVE-2025-31910

HIGH · 7.6 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 1.1.38 or later.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in reputeinfosystems BookingPress bookingpress-appointment-booking allows SQL Injection.This issue affects BookingPress: from n/a through <= 1.1.28.

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

SQL injection vulnerability in the BookingPress WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs in appointment booking forms. The flaw exists in versions through 1.1.28 and could allow unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate BookingPress plugin to the latest version immediately; if unable to update, implement WAF rules to block SQL injection attack patterns and restrict database user privileges.

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
BookingpressWordPress extension
Affected:< 1.1.38

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

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

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. Verify BookingPress plugin is installed
    Check the WordPress plugins directory for the BookingPress plugin folder (wp-content/plugins/bookingpress-appointment-booking) or query the wp_options table for the active_plugins entry containing 'bookingpress'.
    Affected if BookingPress plugin is found in the WordPress installation
  2. Determine installed BookingPress version
    Check the plugin header in wp-content/plugins/bookingpress-appointment-booking/bookingpress.php for the 'Version' field, or query the wp_options table where option_name = 'bookingpress_version'.
    Affected if Version is 1.1.28 or lower, or any version below 1.1.38
  3. Confirm appointment booking forms are publicly accessible
    Navigate to any published BookingPress booking form page or shortcode on the WordPress site to verify the booking functionality is live and accessible to unauthenticated users.
    Affected if Booking forms are published and accessible to visitors without authentication
  4. Check for SQL injection entry points
    Inspect the booking form frontend HTML and identify input fields (such as name, email, phone, or service selection fields) that submit data to the BookingPress AJAX endpoint (admin-ajax.php?action=bookingpress_front_get_category_services).
    Affected if Booking form fields submit directly to BookingPress AJAX handlers without visible sanitization or validation in the page source

A WordPress site is affected if it has BookingPress plugin version below 1.1.38 installed and has publicly accessible appointment booking forms that accept user input.

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
Upgrade available Upgrade to 1.1.38 or later
Fixed in 1.1.38
Interim mitigation

Update BookingPress plugin to the latest version immediately; if unable to update, implement WAF rules to block SQL injection attack patterns and restrict database user privileges.

Recommended fix High confidence

BookingPress 1.1.38 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the BookingPress plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to the latest version (1.1.38 or later)
  5. 5. Alternatively, download BookingPress version 1.1.38 or later from the WordPress plugin repository
  6. 6. Deactivate the existing BookingPress plugin
  7. 7. Upload and install the new version
  8. 8. Reactivate the BookingPress plugin

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

Fix this in Bookingpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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