dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4060

HIGH · 7.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 →
84/100
Remediation priority · High
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
The Geo Mashup plugin for WordPress is vulnerable to Time-Based SQL Injection via the 'sort' parameter in all versions up to, and including, 1.13.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. The `esc_sql()` function is applied but is ineffective in the `ORDER BY` context because the value is not enclosed in quotes. Additionally, while a `sanitize_sort_arg()` allowlist-based sanitizer was added in version 1.13.18, it is only applied in the AJAX code path (`sanitize_query_args()`) and not in the `render-map.php` or template tag code paths. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database via a time-based blind approach.

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 (versions up to 1.13.18) contains a time-based SQL injection vulnerability in the 'sort' parameter. While a sanitize_sort_arg() allowlist-based sanitizer exists in version 1.13.18, it is only applied in the AJAX code path and not in render-map.php or template tag code paths, leaving those paths exploitable. The esc_sql() function is ineffective because the value is not enclosed in quotes in the ORDER BY context, allowing unauthenticated attackers to append malicious SQL queries.

MitigationUpdate to version 1.13.18 or later AND ensure the sanitization fix is applied across ALL code paths (AJAX, render-map.php, and template tags); alternatively, implement proper parameter validation/allowlisting in non-AJAX paths until full patch 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Geo Mashup plugin is installed
    Check the WordPress plugins directory or wp-admin plugins list for 'Geo Mashup' and note the installed version number
    Affected if Plugin is not installed or version is not determinable
  2. Identify the installed version
    Locate the main plugin file (geo-mashup.php or similar) and read the version header, or query the database wp_options table for the 'geo_mashup_version' option
    Affected if Version is 1.13.18 or lower
  3. Determine if non-AJAX code paths are in use
    Search the codebase for includes of 'render-map.php' or usage of template tags such as 'GeoMashup::render_map()' or 'geo_mashup_render_map()' - these indicate non-AJAX paths where the sanitizer may not be applied
    Affected if render-map.php is included or template tag functions are called in theme/custom code
  4. Inspect the sort parameter handling in render-map.php
    If render-map.php exists in the plugin, open it and locate the 'sort' parameter handling - verify whether sanitize_sort_arg() is called before the ORDER BY clause construction
    Affected if sort parameter is processed without sanitize_sort_arg() or the function is absent in this file
  5. Check if the sort parameter is user-controlled
    Review how the sort parameter flows from user input (GET/POST request) to the SQL query - verify whether it reaches the database query without proper allowlist validation in non-AJAX contexts
    Affected if User-supplied 'sort' parameter reaches the ORDER BY clause without allowlist-based validation in render-map.php or template tag paths

The environment is affected if Geo Mashup plugin versions 1.13.18 or lower are installed AND non-AJAX code paths (render-map.php or template tags) are actively used, as the incomplete fix only sanitizes the AJAX route.

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 to version 1.13.18 or later AND ensure the sanitization fix is applied across ALL code paths (AJAX, render-map.php, and template tags); alternatively, implement proper parameter validation/allowlisting in non-AJAX paths until full patch is available.

Recommended fix Moderate confidence

Version after 1.13.19 (contact vendor for exact version with complete fix)

  1. Check the current version of the Geo Mashup plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Geo Mashup and note the current version number
  4. Visit the official WordPress plugin repository or contact the vendor to confirm the latest stable release that fully addresses the SQL injection in all code paths (not just AJAX)
  5. Update the plugin to the latest version that includes complete remediation of the 'sort' parameter sanitization across render-map.php and template tag code paths
  6. Verify the update was successful and test that map functionality works correctly
Caveat Review plugin changelog for any breaking changes before upgrading, particularly if using custom templates or hooks

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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