● High · CVSS 7.5

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

Q: Is CVE-2026-3222 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-3222?

CVSS rates it 7.5 (High). Use that score to set your patch priority next to the other items in your queue.

Q: Do I have to take WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-3222 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-1260: Memory Corruption in Sentencepiece — Memory Corruption in Sentencepiece
How to Fix CVE-2026-4453: Integer overflow in Chrome — Integer overflow in Chrome
How to Fix CVE-2026-5282: Chrome (Bundle Sibling) , Chrome (Bundle Sibling)
How to Fix CVE-2026-5880: Chrome (Bundle Sibling) , Chrome (Bundle Sibling)
How to Fix CVE-2026-8566: Critical Vulnerability in Chrome , Critical Vulnerability in Chrome

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 7.5, High
Actively exploited?	No
Affected	Flippercode WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters (0 <= 4.9.1)
Fixed in	See vendor advisory
Type (CWE)	CWE-89: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

What is CVE-2026-3222?

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 par...

In practical terms, a successful attacker gets SQL injection that can read or modify the backing database. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You're affected if you run Flippercode WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters at any version in the Affected row above. Use these probes to find your installed build:


# Confirm the installed version via your package manager
dpkg -l | grep -i wp   # Debian/Ubuntu
rpm -qa | grep -i wp   # RHEL/CentOS/Rocky

How to fix CVE-2026-3222

The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/b612267c-a125-4153-9de7-bb12a7646021?source=cve
sudo apt-get update
sudo apt-get install --only-upgrade wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters -y
rpm -q wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters

Windows (PowerShell, admin)


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/b612267c-a125-4153-9de7-bb12a7646021?source=cve
# Try winget first
winget upgrade --id 'Flippercode.WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\WPMapsStoreLocatorGoogleMapsOpenStreetMapMapboxListingDirectoryFilters-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows) - detect, back up, upgrade, verify, log


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/b612267c-a125-4153-9de7-bb12a7646021?source=cve
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\WPMapsStoreLocatorGoogleMapsOpenStreetMapMapboxListingDirectoryFilters-Patch-CVE-2026-3222.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-3222 remediation for Flippercode WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*WP*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'<patched-version>') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\WPMapsStoreLocatorGoogleMapsOpenStreetMapMapboxListingDirectoryFilters-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Flippercode\WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\WPMapsStoreLocatorGoogleMapsOpenStreetMapMapboxListingDirectoryFilters-<patched-version>.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*WP*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
    Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux) - detect, back up, upgrade, verify, log


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/b612267c-a125-4153-9de7-bb12a7646021?source=cve
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters-patch-cve-2026-3222.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-3222 remediation for Flippercode WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters)
    PKG_MGR=dnf
else
    log "wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters
else
    sudo dnf upgrade --security -y wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters)
fi
log "After upgrade: $NEW"

# Optionally compare against <patched-version> with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."

If you can't patch immediately

These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.

Block obvious SQL injection patterns with a WAF rule


# ModSecurity / OWASP CRS-style rule
SecRule ARGS "@rx (?i)(union(.|\n)+?select|select(.|\n)+?from|insert(.|\n)+?into)" \
  "id:900100,phase:2,deny,log,msg:'SQLi pattern blocked'"

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


# Confirm the running build matches the patched version listed by the vendor
# Example for Linux package installs:
dpkg -l | grep -i "wp"   # Debian/Ubuntu
rpm -qa | grep -i "wp"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed the patched build.

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-3222 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-3222 being actively exploited?