dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49891

HIGH · 8.5 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 uxper Uxper Booking uxper-booking allows Blind SQL Injection.This issue affects Uxper Booking: from n/a through <= 1.3.3.

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

A blind SQL injection vulnerability exists in uxper Uxper Booking plugin (versions <= 1.3.3) where user-supplied input is not properly sanitized before being used in SQL queries. An unauthenticated attacker can inject malicious SQL statements through vulnerable parameters, potentially extracting sensitive data from the database by observing boolean-based or time-based responses.

MitigationUpgrade to a patched version of Uxper Booking that properly implements parameterized queries or prepared statements for all database interactions, and implement input validation as a defense-in-depth measure.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm the uxper-booking plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'uxper-booking', or check the wp-content/plugins/uxper-booking/ directory exists on the server
    Affected if The plugin is not present in the installed plugins list or the plugin directory does not exist on the server
  2. Identify the installed plugin version
    Open the plugin's main PHP file (usually uxper-booking.php) or the readme.txt file in wp-content/plugins/uxper-booking/ and locate the version declaration comment
    Affected if The version displayed matches any vulnerable version range for this CVE (compare your installed version to the affected ranges)
  3. Verify booking functionality is accessible
    Check if the booking feature is enabled in the plugin settings, or attempt to access the booking form endpoint on the frontend of the site (usually at a URL containing /booking/ or similar)
    Affected if The booking functionality is active and accepts user input through form fields
  4. Inspect booking-related PHP files for unsanitized SQL queries
    Examine PHP files in wp-content/plugins/uxper-booking/ that handle booking submissions (typically files with 'booking', 'submit', or 'form' in the name) and look for direct SQL query construction using user-supplied $_POST or $_GET parameters without prepared statements
    Affected if Code review reveals SQL queries built using concatenation or interpolation of raw user input without parameterized queries
  5. Test for blind SQL injection in booking parameters
    Submit booking form data with boolean-based payloads in parameter fields (e.g., adding AND 1=1 vs AND 1=2, or time-delay functions like SLEEP() in parameter values) and observe differences in response times or behavior
    Affected if Response times or application behavior differs based on injected boolean conditions, indicating the parameter is not properly sanitized before use in SQL queries

You are affected if the uxper-booking plugin is installed with a vulnerable version, the booking functionality is enabled, and user input in booking forms is used in SQL queries without sanitization or parameterized queries.

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

Upgrade to a patched version of Uxper Booking that properly implements parameterized queries or prepared statements for all database interactions, and implement input validation as a defense-in-depth measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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