dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22537

HIGH · 8.5 CVSS v3.1 Published 2025-01-09
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 traveller11 Google Maps Travel Route google-maps-travel-route allows SQL Injection.This issue affects Google Maps Travel Route: from n/a through <= 1.3.1.

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

SQL injection vulnerability in traveller11 Google Maps Travel Route plugin (versions <= 1.3.1) allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized data access, modification, or deletion from the database.

MitigationReplace dynamic SQL query construction with parameterized queries (prepared statements) and implement strict input validation on all user-supplied data before use in database operations.

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. Identify if traveller11 Google Maps Travel Route plugin is installed
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Google Maps Travel Route' or 'traveller11'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'traveller11' or 'google-maps-travel-route' in the name.
    Affected if The plugin appears in the list of installed plugins, regardless of activation status.
  2. Determine the installed plugin version
    In the WordPress Plugins list, click on the plugin name to view its details, or check the plugin's main PHP file header for the 'Version' comment. Common file paths include /wp-content/plugins/google-maps-travel-route/ or /wp-content/plugins/traveller11-google-maps/.
    Affected if The displayed version number is 1.3.1 or lower.
  3. Confirm the plugin is actively enabled
    In the WordPress admin, verify that the plugin shows as 'Active' in the Plugins list. An active plugin processes requests and can be exploited.
    Affected if The plugin status is 'Active'.
  4. Check for exposure of the vulnerable parameter
    Review publicly accessible URLs that invoke the plugin's functionality. The vulnerability stems from unsanitized user input in database operations. Examine plugin shortcodes or AJAX endpoints that accept user-supplied values (common parameters include route_id, id, or similar identifiers).
    Affected if The plugin exposes frontend-facing features (shortcodes, AJAX handlers, or public forms) that accept user input for database queries.
  5. Review application logs for SQL injection indicators
    Examine web server access logs and WordPress debug logs (/wp-content/debug.log if enabled) for unusual SQL syntax, UNION SELECT patterns, or error messages containing 'SQL syntax' near plugin-related URLs.
    Affected if Logs contain SQL error messages or suspicious query patterns targeting plugin endpoints.

You are affected if the traveller11 Google Maps Travel Route plugin is installed at version 1.3.1 or lower and the plugin is active with publicly accessible features that accept user input for database operations.

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

Replace dynamic SQL query construction with parameterized queries (prepared statements) and implement strict input validation on all user-supplied data before use in database operations.

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-22537 — 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-22537 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