CVE-2026-116519 json
Geo Mashup <= 1.13.23 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name and User Display Name
published 13h ago modified 3h ago also EUVD-2026-128848
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
The Geo Mashup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author (comment form) / display_name (profile form)' parameter in all versions up to, and including, 1.13.23 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The comment-author path requires the crafted comment to be approved before the payload is served to visitors; the subscriber-level path requires the plugin's user-location mapping feature to be enabled.
Is CVE-2026-116519 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- cyberhobo Geo Mashup
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/a8c4fcfd-fa59-41f6-a852-02220bf995ff?source=cve
- plugins.trac.wordpress.org /browser/geo-mashup/tags/1.13.23/js/geo-mashup.js#L924
- plugins.trac.wordpress.org /browser/geo-mashup/tags/1.13.23/js/geo-mashup.js#L871
- plugins.trac.wordpress.org /browser/geo-mashup/tags/1.13.23/geo-mashup.php#L892
- plugins.trac.wordpress.org /browser/geo-mashup/tags/1.13.23/geo-mashup-db.php#L392
- plugins.trac.wordpress.org /browser/geo-mashup/tags/1.13.23/geo-mashup-ui-managers.php#L1015
- plugins.svn.wordpress.org /geo-mashup/tags/1.13.24/
Sources
- CVE List CVE-2026-116519
- NVD CVE-2026-116519
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.