Quick answers
- Is CVE-2026-6381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6381 being exploited in the wild.
- How severe is CVE-2026-6381?
- Informational severity, with a CVSS score of 7.5, published 18 May 2026.
- Which products and versions are affected?
- WP Maps < 4.9.3.
- Is there a fix for CVE-2026-6381?
- A patch was published on 2026-04-27: Fix released in version 4.9.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6381 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6381?
- Check whether you run WP Maps at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WP Maps plugin for WordPress (wp-google-map-plugin) fails to properly sanitize a specific parameter before it is used in a file path operation. This vulnerability, classified as CWE-22 (Path Traversal), allows authenticated attackers with at least Subscriber-level privileges to perform Local File Inclusion (LFI) attacks. By manipulating the affected parameter, an attacker can read arbitrary files from the server's filesystem that the web server process has permissions to access. The issue is resolved in version 4.9.3.
Affected products
- WP Maps WP Maps (wp-google-map-plugin) < 4.9.3
Timeline
- 2026-04-27: disclosed: Vulnerability publicly disclosed by WPScan
- 2026-04-27: patched: Fix released in version 4.9.3
- 2026-05-18: advisory: NVD published the CVE record