dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-39504

CRITICAL · 9.3 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in GoodLayers Goodlayers Hotel gdlr-hotel allows Blind SQL Injection.This issue affects Goodlayers Hotel: from n/a through <= 3.1.4.

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 the GoodLayers Hotel plugin (gdlr-hotel) versions up to 3.1.4. The vulnerability allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpdate the Goodlayers Hotel plugin to the latest patched version as soon as available. If no patch exists, implement parameterized queries or prepared statements to sanitize user input before executing SQL commands, and consider temporarily disabling the plugin until a fix is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the GoodLayers Hotel plugin version
    Access your WordPress admin panel and navigate to Plugins > Installed Plugins. Find 'GoodLayers Hotel' (gdlr-hotel) and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/goodlayers-hotel/) for the 'Version' header comment.
    Affected if The displayed version is 3.1.4 or any version earlier than 3.1.4.
  2. Verify the plugin is active
    In the WordPress admin panel under Plugins > Installed Plugins, confirm that the GoodLayers Hotel plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and processing requests.
  3. Identify user input handling points
    Inspect the plugin's PHP files, particularly those handling booking, search, or form submissions (commonly found in includes/ or shortcodes/ directories). Look for SQL queries that directly incorporate $_GET, $_POST, or $_REQUEST parameters without apparent sanitization.
    Affected if The plugin directly uses user-supplied input in SQL queries without prepared statements or input validation.
  4. Check for vulnerable booking/search parameters
    Review the plugin's booking form handlers and search functionality. Common vulnerable areas include room availability checks, booking submissions, and guest information fields. Verify whether these endpoints validate or sanitize input before executing database queries.
    Affected if User-accessible booking or search forms exist and accept input that flows directly into SQL statements.

You are affected if the GoodLayers Hotel plugin version is 3.1.4 or earlier, the plugin is active, and it processes user input through SQL queries without proper sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Goodlayers Hotel plugin to the latest patched version as soon as available. If no patch exists, implement parameterized queries or prepared statements to sanitize user input before executing SQL commands, and consider temporarily disabling the plugin until a fix is available.

Recommended fix Moderate confidence

Latest version of Goodlayers Hotel (version > 3.1.4)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Goodlayers Hotel' (gdlr-hotel).
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. Alternatively, download the latest version from the official WordPress repository or the theme developer's website.
  7. 7. After updating, verify the plugin is running on the newest version.
  8. 8. Test critical hotel booking functionality to ensure the update did not break existing features.
Caveat Minor version updates typically include bug fixes; review the changelog for any feature changes that may affect your site.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,660
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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