⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.5

How to Fix CVE-2026-2580: SQL Injection in WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters

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

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 7.5 - High
Actively exploited?Not currently listed in CISA KEV
Affected0 <= 4.9.1
Fixed inSee vendor advisory
Type (CWE)CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

What is CVE-2026-2580?

CVE-2026-2580 is a SQL injection flaw in WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters. User input reaches a database query without proper parameterization, letting an attacker read, modify, or in some cases execute commands through stacked queries or out-of-band channels. Vendor description: The WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters plugin for WordPress is vulnerable to time-based SQL Injection via the ‘orderby’ parameter in all versions up to, and including, 4.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL 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.

Why this CVE matters

SQL injection against a management product is rarely just a data leak. Once an attacker can read or write to the application database, the chain commonly ends with credential theft, persistence via scheduled tasks, or stacked queries that pivot into the operating system.

For deployments of WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-2580

  1. Read the vendor advisory in full: https://www.wordfence.com/threat-intel/vulnerabilities/id/8d954868-eff2-497d-84e7-cc42da8a4c6f?source=cve
  2. Upgrade WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
  5. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  6. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Patched-version commands

Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/8d954868-eff2-497d-84e7-cc42da8a4c6f?source=cve

Affected: WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters: 0 <= 4.9.1

Patched in: 4.9.1


# WordPress / WP-CLI on the server.
# Update the plugin or theme to the patched release named in the advisory above.
wp plugin update wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters --version=4.9.1

# Or update every installed plugin to its latest release.
wp plugin update --all

# If you cannot patch immediately, deactivate the vulnerable plugin.
wp plugin deactivate wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters

# Verify the running version.
wp plugin get wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters --field=version


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/8d954868-eff2-497d-84e7-cc42da8a4c6f?source=cve
# From a Windows admin workstation via SSH.
ssh wpadmin@<your-wp-host> "wp plugin update wp-maps---store-locator-google-maps-openstreetmap-mapbox-listing-directory---filters --version=4.9.1"

Verify the fix landed


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/8d954868-eff2-497d-84e7-cc42da8a4c6f?source=cve
# Post-patch verification (replace <service> with the real service unit).
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
# It should no longer flag CVE-2026-2580 on the patched target.

If you cannot patch immediately

Front the affected endpoint with a WAF rule that blocks SQL metacharacters in the vulnerable parameters. This is a stopgap, not a fix. Patch promptly.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-2580 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-2580?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*