CVE-2026-84780

WP Go Maps – Google Map, OpenStreetMap, Leaflet Map <= 10.1.08 - Unauthenticated Denial of Service

2026-09-02 00:00
Asim Alshaya

Strategic Overview

Status
Patched in 10.1.09
Affected Plugin
WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
Affected Version
<= 10.1.08
CVSS
7.5High
Weakness type
CWE-400 · Uncontrolled Resource Consumption
CVE
CVE-2026-84780
View all WP Go Maps – Google Map, OpenStreetMap, Leaflet Map vulnerabilities

At a glance

CVE-2026-84780 is a high-severity Uncontrolled Resource Consumption vulnerability in the WP Go Maps WordPress plugin, affecting versions <= 10.1.08. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 10.1.09; sites on affected versions should update now. Disclosed September 2026, reported by Asim Alshaya.

Vulnerability Overview

The WP Go Maps – Google Map, OpenStreetMap, Leaflet Map plugin for WordPress is vulnerable to Denial of Service in all versions up to, and including, 10.1.08. This is due to insufficient validation of user supplied input. This makes it possible for unauthenticated attackers to make the affected site unavailable.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on availability.

CWE-400: Uncontrolled Resource Consumption

Reaching this weakness in WP Go Maps <= 10.1.08 takes no account at all. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.

A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. For WP Go Maps the fix is 10.1.09: builds <= 10.1.08 are affected, anything from 10.1.09 onward is not.

Remediation

Update to version 10.1.09, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Go Maps 10.1.09 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-84780https://www.wordfence.com/threat-intel/vulnerabilities/id/2c91f611-8529-4053-8faf-d23a213dd569https://nvd.nist.gov/vuln/detail/CVE-2026-84780

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C