CVE-2026-84780: WP Go Maps denial of service in map rendering

CVE-2026-84780 · Severity: medium · CVSS 5.3 · Published 2026-09-02

WP Go Maps is a popular WordPress plugin that displays interactive maps on websites. An unauthenticated attacker can send specially crafted requests to the plugin, overwhelming the server and causing the website to become slow or go offline. This vulnerability requires no special privileges and can be exploited by anyone over the network.

Technologies: WP Go Maps. Vendors: WP Go Maps.

Quick answers

Is CVE-2026-84780 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-84780 being exploited in the wild.
How severe is CVE-2026-84780?
Medium severity, with a CVSS score of 5.3, published 2 September 2026.
Which products and versions are affected?
WP Go Maps <= 10.1.08.
Is there a fix for CVE-2026-84780?
A patch was published on 2026-09-02: Patched in version 10.1.09 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-84780 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-84780?
Check whether you run WP Go 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

This vulnerability is a denial of service (DoS) attack in WP Go Maps versions 10.1.08 and earlier, classified as an insecure design flaw. The plugin fails to properly validate or rate-limit unauthenticated requests to a critical component, allowing an attacker to send a flood of malicious requests that consume server resources. No authentication is required to exploit this vulnerability. The attack can render the website unavailable to legitimate users. The vendor has patched this issue in version 10.1.09; affected users should update immediately.

Affected products

  • WP Go Maps WP Go Maps <= 10.1.08

Timeline

  • 2026-09-02: disclosed: Published by Patchstack
  • 2026-09-02: patched: Patched in version 10.1.09

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.