dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-6457

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-02
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 Geo Mashup plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'geo_mashup_null_fields' parameter in all versions up to, and including, 1.13.19 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 subscriber-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 Geo Mashup WordPress plugin up to version 1.13.19 contains a time-based blind SQL injection vulnerability in the 'geo_mashup_null_fields' parameter. The parameter is not properly escaped before being used in an SQL query, and the existing query lacks prepared statements, allowing authenticated attackers with subscriber-level access to inject arbitrary SQL code and extract sensitive data from the database.

MitigationUpdate the Geo Mashup plugin to a version beyond 1.13.19 when a patched release becomes available. If no patched version exists, disable the plugin or implement input validation/waf rules for the affected parameter as a temporary 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
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. Verify Geo Mashup plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Geo Mashup' in the list of active plugins.
    Affected if Geo Mashup plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins list, click on 'Geo Mashup' details or view the plugin file header (usually geo-mashup.php) to find the version number.
    Affected if The installed version is 1.13.19 or lower
  3. Determine if subscriber-level accounts exist
    Navigate to WordPress admin > Users. Review user roles to see if any users have 'Subscriber' role or higher (Contributor, Author, Editor, Administrator).
    Affected if Any user account with Subscriber role or higher exists in the WordPress installation
  4. Verify parameter is accessible
    The vulnerability exists in the 'geo_mashup_null_fields' parameter. This parameter is used in plugin queries. Check if the plugin functionality that uses this parameter is enabled or actively used on the site.
    Affected if The plugin is active and the parameter functionality is in use (e.g., maps or location-based queries are displayed)

A user is affected if the Geo Mashup plugin version is 1.13.19 or lower AND any subscriber-level user account exists AND the plugin functionality using the vulnerable parameter is active.

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 Geo Mashup plugin to a version beyond 1.13.19 when a patched release becomes available. If no patched version exists, disable the plugin or implement input validation/waf rules for the affected parameter as a temporary measure.

Recommended fix Moderate confidence

Geo Mashup plugin version 1.13.20 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Geo Mashup plugin
  4. Click 'Update Now' if an update is available, or manually upload version 1.13.20 or later of the plugin

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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