CVE-2026-3222 json
WP Maps <= 4.9.1 - Unauthenticated SQL Injection via 'location_id' Parameter
published 7mo ago modified 4mo ago also EUVD-2026-11103
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-3222 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- flippercode WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/b612267c-a125-4153-9de7-bb12a7646021?source=cve
- plugins.trac.wordpress.org /browser/wp-google-map-plugin/tags/4.9.1/wp-google-map-plugin.php#L250
- plugins.trac.wordpress.org /browser/wp-google-map-plugin/trunk/wp-google-map-plugin.php#L250
- plugins.trac.wordpress.org /browser/wp-google-map-plugin/tags/4.9.1/wp-google-map-plugin.php#L590
- plugins.trac.wordpress.org /browser/wp-google-map-plugin/trunk/wp-google-map-plugin.php#L590
- plugins.trac.wordpress.org /browser/wp-google-map-plugin/tags/4.9.1/core/class.model.php#L328
- plugins.trac.wordpress.org /browser/wp-google-map-plugin/trunk/core/class.model.php#L328
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=3475665%40wp-google-map-plugin%2Ftrunk&old=3439153%40wp-google-
- plugins.trac.wordpress.org /changeset/3475665/wp-google-map-plugin/trunk/wp-google-map-plugin.php
- plugins.trac.wordpress.org /changeset/3475665/wp-google-map-plugin/trunk/core/class.model.php
Sources
- CVE List CVE-2026-3222
- NVD CVE-2026-3222
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.