CVE-2026-3222 HIGH

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

Vendor Flippercode
Product WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters
Weakness CWE-89 · SQLi
Published March 11, 2026
Last update April 8, 2026

CVSS base score

7.5/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity None

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

WP Maps – Store Locator contains a SQL injection vulnerability in versions up to 4.9.1. An attacker can craft a malicious request to extract sensitive data from the site's database without authentication. The vulnerability requires no user interaction and can be exploited remotely over the network.

What an attacker can do

03Attacker Capabilities

Extract sensitive data from the site's database, including user credentials and private information.

Potential impact on your site

04Site Impact

Attackers can read your database contents, potentially exposing user data, credentials, and private information.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

March 11, 2026 CVE published
April 8, 2026 Record updated