What’s Vulnerable › Vulnerabilities

CVE-2026-13456: WP Maps <= 4.9.8 - Authenticated (Subscriber+) Local File Inclusion via 'page' Parameter

• Severity: high (CVSS 7.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.8% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-25 · updated 2026-09-25
• Weakness: CWE-98

Description

The WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.9.8 via the 'page' parameter parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

Affected products

• flippercode WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings: through 4.9.8

References

• https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/core/class.controller.php#L115
• https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/wp-google-map-plugin.php#L605
• https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/wp-google-map-plugin.php#L622
• https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/core/class.controller.php#L115
• https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/wp-google-map-plugin.php#L605
• https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/wp-google-map-plugin.php#L622
• https://plugins.trac.wordpress.org/changeset?reponame=&old=3690856%40wp-google-map-plugin&new=3690856%40wp-google-map-plugin
• https://www.wordfence.com/threat-intel/vulnerabilities/id/404a3124-bff7-4d92-8424-5b21382031f2?source=cve

Get alerted when CVE-2026-13456 or the next vulnerability affects your stack