dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3222

HIGH · 7.5 CVSS v3.1 Published 2026-03-11
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 WP Maps plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'location_id' parameter in all versions up to, and including, 4.9.1. This is due to the plugin's database abstraction layer (`FlipperCode_Model_Base::is_column()`) treating user input wrapped in backticks as column names, bypassing the `esc_sql()` escaping function. Additionally, the `wpgmp_ajax_call` AJAX handler (registered for unauthenticated users via `wp_ajax_nopriv`) allows calling arbitrary class methods including `wpgmp_return_final_capability`, which passes the unsanitized `location_id` GET parameter directly to a database query. 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.

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 Maps WordPress plugin (versions up to 4.9.1) contains a time-based blind SQL injection vulnerability in the 'location_id' parameter. The FlipperCode_Model_Base::is_column() database abstraction method incorrectly treats backtick-wrapped user input as column names, bypassing esc_sql() escaping. The unauthenticated AJAX handler wpgmp_ajax_call allows calling arbitrary class methods, including wpgmp_return_final_capability which passes the unsanitized location_id directly to SQL queries.

MitigationUpdate WP Maps to the latest version; if no patched version exists, disable the plugin until a fix is available, or implement a WAF rule to block SQL injection attempts targeting the location_id 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. Locate WP Maps plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-maps' or similar. Inspect the main plugin file header for the 'Version' field, or check readme.txt for the stable tag.
    Affected if The plugin is installed and the version is 4.9.1 or lower (any version up to 4.9.1 is affected)
  2. Identify the vulnerable AJAX handler
    Search the plugin source code for 'wpgmp_ajax_call' to locate where the AJAX handler is registered. Verify the presence of 'wp_ajax_wpgmp_ajax_call' and 'wp_ajax_nopriv_wpgmp_ajax_call' hooks in the plugin files.
    Affected if The AJAX handler is registered, meaning unauthenticated attackers can invoke class methods via this endpoint
  3. Verify the FlipperCode_Model_Base class exists
    Search the plugin code for 'FlipperCode_Model_Base' and its 'is_column' method. This is the vulnerable database abstraction method that mishandles backtick-wrapped input.
    Affected if The FlipperCode_Model_Base::is_column method is present and used in the plugin's codebase
  4. Confirm location_id reaches the SQL query
    Locate the 'wpgmp_return_final_capability' method in the plugin. Trace how the 'location_id' parameter flows from the AJAX request through to the SQL query without proper sanitization.
    Affected if The location_id parameter is passed unsanitized to SQL queries via the wpgmp_return_final_capability method

If WP Maps version 4.9.1 or lower is installed with the wpgmp_ajax_call endpoint accessible and the FlipperCode_Model_Base class present, the environment is affected by this SQL injection vulnerability.

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 WP Maps to the latest version; if no patched version exists, disable the plugin until a fix is available, or implement a WAF rule to block SQL injection attempts targeting the location_id parameter.

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-3222 — 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-3222 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