LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3222: WP Maps <= 4.9.1 - Unauthenticated SQL Injection via 'location_id' Parameter

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-3222 affects the WP Maps WordPress plugin through version 4.9.1. An unauthenticated internet user may be able to make the site database answer unintended queries, potentially exposing sensitive data. This is a high-priority issue for any public WordPress site using this plugin.

Executive priority

Prioritize within the next patch cycle, faster for public sites handling customer, user, or business data. The main business risk is database information disclosure without attacker login. If the plugin supports critical store-locator or map features, plan a controlled update or temporary disablement with business-owner coordination.

Technical view

The flaw is a time-based blind SQL injection in the location_id parameter. The cited description says an unauthenticated AJAX handler can call methods that pass unsanitized input into database queries. The database abstraction layer treats backtick-wrapped input as column names, bypassing escaping. CVSS is 7.5, with network access, low complexity, no privileges, and high confidentiality impact.

Likely exposure

Exposure is likely for internet-facing WordPress sites running WP Maps / wp-google-map-plugin versions up to and including 4.9.1. The vulnerable path is unauthenticated, so login is not required. Confirm exposure by checking plugin presence and version rather than assuming all WordPress sites are affected.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is still serious because it is unauthenticated, network-reachable, and affects database confidentiality. The described class-method dispatch and SQL handling issues increase practical exposure for public sites.

Researcher notes

Key areas are wp_ajax_nopriv exposure, wpgmp_ajax_call method dispatch, wpgmp_return_final_capability, location_id handling, and FlipperCode_Model_Base::is_column(). The provided sources indicate a code change in WordPress Trac, but do not name a fixed release version. Avoid claiming exploitation unless new evidence appears.

Mitigation direction

  • Inventory WordPress sites for WP Maps / wp-google-map-plugin installations.
  • Upgrade to a vendor-provided fixed version when available.
  • Confirm the installed code includes the Trac changeset 3475665 fixes.
  • If no fixed release is available, consider disabling the plugin temporarily.
  • Restrict direct internet access to affected sites where business-feasible.
  • Monitor vendor, Wordfence, and WordPress plugin guidance for updates.

Validation and detection

  • Check each site’s installed WP Maps plugin version.
  • Treat versions up to and including 4.9.1 as affected.
  • Review whether relevant files include changes from Trac changeset 3475665.
  • Verify unauthenticated AJAX exposure is not reachable after remediation.
  • Review web and database logs for unusual requests involving location_id.
  • Document remediation status per WordPress instance.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3222 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-3222Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
flippercodeWP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters0unaffected
Weakness

CWE details

CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.