Skip to main content
VulnerabilityPublished

CVE-2026-116519: Geo Mashup (WordPress plugin) · Cross-site Scripting

Affects Geo Mashup (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 18 Nov 2026, 14:51 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
cyberhoboGeo MashupAffected
  • <=1.13.23
Fixed in–

AI-suggested

Users should monitor the vendor's advisories for updates. Until a fix is available, administrators should consider disabling the comment feature or the user-location mapping feature if enabled, and carefully review and moderate comments to prevent malicious payloads from being approved. Applying strict input validation and output escaping via custom code or security plugins may mitigate risk.

Description

The Geo Mashup WordPress plugin up to version 1.13.23 is vulnerable to stored Cross-Site Scripting (XSS) via the 'author' parameter in the comment form and the 'display_name' parameter in the profile form. This vulnerability allows unauthenticated attackers to inject malicious scripts that execute when users view the affected pages. Exploitation via the comment-author path requires comment approval, while the subscriber-level path requires the user-location mapping feature to be enabled.

References

Community reviews

Loading reviews…