dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4061

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 'map_post_type' parameter in all versions up to, and including, 1.13.18. This is due to the `SearchResults` hook explicitly calling `stripslashes_deep($_POST)` which removes WordPress magic quotes protection, followed by the unsanitized `map_post_type` value being concatenated into an `IN(...)` clause without `esc_sql()` or `$wpdb->prepare()`. The 'any' branch of the same code correctly applies `array_map('esc_sql', ...)`, but the else branch does not. 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. Exploitation requires the Geo Search feature to be enabled in plugin settings.

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 SearchResults hook. The 'map_post_type' POST parameter is processed through stripslashes_deep() which removes WordPress magic quotes protection, then concatenated directly into an IN(...) SQL clause without esc_sql() or $wpdb->prepare() sanitization, allowing unauthenticated attackers to inject arbitrary SQL queries.

MitigationUpdate Geo Mashup plugin to version 1.13.19 or later. Until an official patch is available, disable the Geo Search feature in plugin settings and consider deploying a WAF rule to block SQL injection attempts against the map_post_type parameter.

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. Verify Geo Mashup plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the geo-mashup folder, or query the wp_plugins table for 'geo-mashup' active plugin entry.
    Affected if Geo Mashup plugin is not present in the WordPress installation.
  2. Identify installed Geo Mashup version
    Read the plugin header from geo-mashup.php file in the plugin directory, or query wp_options for the 'geo_mashup_version' option if stored, or check the plugin file's Version: field.
    Affected if The installed version is 1.13.18 or lower.
  3. Confirm Geo Search feature is enabled
    Query the wp_options table for option_name containing 'geo_mashup' (such as 'geo_mashup_options' or 'geo_mashup_search_settings') and check if the search-related feature is turned on in the configuration.
    Affected if The Geo Search or SearchResults functionality is enabled in plugin settings.
  4. Check for SQL injection attempts in logs
    Review WordPress debug logs, server access logs, or WAF logs for POST requests to any SearchResults endpoint containing the 'map_post_type' parameter with unusual characters (quotes, dashes, SQL keywords).
    Affected if Suspicious SQL injection patterns found in logs for the map_post_type parameter.

You are affected if Geo Mashup plugin version 1.13.18 or lower is installed AND the Geo Search feature is enabled, allowing unauthenticated SQL injection via the map_post_type POST parameter.

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 Geo Mashup plugin to version 1.13.19 or later. Until an official patch is available, disable the Geo Search feature in plugin settings and consider deploying a WAF rule to block SQL injection attempts against the map_post_type parameter.

Recommended fix High confidence

Geo Mashup version > 1.13.18 (check WordPress plugin repository for latest release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Geo Mashup plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest fixed version
  5. 5. Verify the update was successful by checking the plugin version (should be greater than 1.13.18)
  6. 6. Confirm the Geo Search feature is still functioning correctly after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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