dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-11365

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The WP Google Map Plugin plugin for WordPress is vulnerable to blind SQL Injection via the 'id' parameter of the 'google_map' shortcode in all versions up to, and including, 1.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The WP Google Map Plugin for WordPress is vulnerable to blind SQL injection in versions up to 1.0. The 'id' parameter of the 'google_map' shortcode is not properly escaped, and the underlying SQL query lacks prepared statements. This allows authenticated users with Contributor-level access or higher to inject arbitrary SQL queries.

MitigationUpdate the plugin to the latest patched version once available. Until then, restrict the contributor-level role to trusted users only, and consider deploying a WAF rule to detect and block SQL injection patterns in the shortcode parameters.

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

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

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 WP Google Map Plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check /wp-content/plugins/ directory for the google-map plugin folder
    Affected if The WP Google Map Plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In WordPress admin, click 'View Details' on the WP Google Map Plugin, or read the version in the plugin's main PHP file header (usually in the plugin folder root)
    Affected if The version is 1.0 or any version up to and including 1.0 (no version greater than 1.0 is listed as fixed)
  3. Check for use of the google_map shortcode
    Search WordPress database wp_posts table for content containing '[google_map' shortcode, or use a plugin to scan posts/pages for shortcode usage
    Affected if Any post, page, or custom post type contains the [google_map] shortcode with an 'id' parameter
  4. Verify Contributor-level user accounts exist
    In WordPress admin, go to Users > All Users and review the role column, or query wp_usermeta and wp_users tables for users with 'contributor' capability
    Affected if There is at least one user account with Contributor role or higher (Author, Editor, Admin)
  5. Inspect the shortcode handler code
    Locate the plugin's shortcode handler function (search for 'add_shortcode' and 'google_map' in the plugin PHP files), then examine how the 'id' attribute is handled in the SQL query - look for direct variable insertion without $wpdb->prepare() or similar sanitization
    Affected if The 'id' parameter is used directly in an SQL query without prepare() or proper escaping/validation

The environment is affected if the WP Google Map Plugin version 1.0 or below is installed, the google_map shortcode with an id parameter is in use, and any user with Contributor-level or higher access exists on the site.

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

Update the plugin to the latest patched version once available. Until then, restrict the contributor-level role to trusted users only, and consider deploying a WAF rule to detect and block SQL injection patterns in the shortcode parameters.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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