dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4062

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 'object_ids' and 'exclude_object_ids' parameters in all versions up to, and including, 1.13.18. This is due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL query. The `esc_sql()` function is applied but is ineffective because the values are placed in an unquoted `IN(...)` / `NOT IN(...)` SQL context — `esc_sql()` only escapes quote characters and provides no protection against parenthesis or SQL keyword injection. Additionally, while a numeric-only sanitizer exists in `sanitize_query_args()`, it is only applied in the AJAX code path 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 <= 1.13.18 is vulnerable to time-based SQL injection via the 'object_ids' and 'exclude_object_ids' parameters. The `esc_sql()` function provides no protection because these parameters are placed in unquoted IN(...)/NOT IN(...) SQL context where quotes are not required. A numeric-only sanitizer exists but is only applied in the AJAX code path, leaving render-map.php and template tag paths vulnerable. Unauthenticated attackers can inject additional SQL queries to extract sensitive data via blind time-based techniques.

MitigationUpdate Geo Mashup plugin to version 1.13.19 or later, or disable the plugin until patched.

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
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Geo Mashup' in the list
    Affected if Geo Mashup plugin appears in the installed plugins list
  2. Identify installed version of Geo Mashup
    In the Plugins list, locate the Geo Mashup plugin and note the version number displayed below the plugin name. Alternatively, check the main plugin file (geo-mashup.php) in wp-content/plugins/geo-mashup/ for the Version header comment
    Affected if Version is 1.13.18 or lower
  3. Verify render-map.php exists in plugin directory
    Check for the presence of render-map.php in the wp-content/plugins/geo-mashup/ directory via file manager or FTP
    Affected if File exists at wp-content/plugins/geo-mashup/render-map.php and plugin version is vulnerable
  4. Detect usage of vulnerable parameter object_ids
    Review web server access logs for GET or POST requests containing 'object_ids' parameter, particularly in unauthenticated contexts or requests to render-map.php
    Affected if Requests with object_ids parameter are being processed by the plugin
  5. Detect usage of vulnerable parameter exclude_object_ids
    Review web server access logs for GET or POST requests containing 'exclude_object_ids' parameter
    Affected if Requests with exclude_object_ids parameter are being processed by the plugin

The environment is affected if Geo Mashup plugin version 1.13.18 or lower is installed and requests containing object_ids or exclude_object_ids parameters are being handled by render-map.php or template tags.

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, or disable the plugin until patched.

Recommended fix Moderate confidence

1.13.19 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Geo Mashup plugin
  4. Click 'Update Now' if an update is available, or manually download version 1.13.19 or later from wordpress.org/plugins/geo-mashup/ and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the version number shows 1.13.19 or higher under Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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