Skip to main content

Geo Mashup CVE-2026-78294

| EUVDEUVD-2026-81518 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-09-17 Patchstack GHSA-28gp-m9rr-mwp4
6.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Contributor account on target site
  2. Delivery
    Inject XSS payload via Geo Mashup input
  3. Exploit
    Admin/editor views the content
  4. Execution
    Script executes in privileged session
  5. Impact
    Hijack session or perform admin actions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a working Contributor-level (or higher) authenticated account on the target WordPress site, so it is exploitable only where untrusted users can obtain such accounts (multi-author blogs, membership/community sites). Exploitation further depends on the Geo Mashup plugin (<=1.13.21) being installed and active, and on a second victim user with a more privileged session viewing the attacker's injected content (UI:R). It does NOT work against default single-admin installations with no untrusted contributors, and cannot be triggered by fully unauthenticated remote attackers.

Impact

This is a moderate-severity, authenticated stored/injected XSS in the Geo Mashup WordPress plugin (<=1.13.21), reported by Patchstack. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, base 6.5) tells a consistent story: network-reachable, low complexity, but requiring low-privilege authentication (PR:L) and victim interaction (UI:R). The PR:L combined with the 'Contributor' qualifier in the title means an attacker must already hold a Contributor-level account, which sharply narrows the real-world attacker population versus an unauthenticated flaw. The scope change (S:C) reflects script executing in another user's browser context (e.g. an admin previewing content), yielding the low-but-broad C:L/I:L/A:L impacts typical of XSS. On exploitation signals: no EPSS score, no CISA KEV listing, and no public POC were provided - so exploitation status is 'no public exploit identified at time of analysis.' There is no conflict between the CVSS vector and the description; both indicate authenticated, interaction-dependent web exploitation. Net: this is a real but lower-priority issue - a self-service (Contributor) foothold plus an admin viewing the malicious content is required, making it more relevant to multi-author sites than a mass-exploitable perimeter bug.

Exploit ScenarioDerived

An attacker who has registered or been granted a Contributor account on a multi-author WordPress site submits content or geo/map field input containing a malicious script payload through Geo Mashup. When a higher-privileged user (e.g. an editor or administrator) previews or views that content in wp-admin, the script executes in their authenticated session, potentially performing actions as that user. No public POC or active exploitation was reported at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 17, 2026

Stored cross-site scripting in the Geo Mashup plugin for WordPress (versions through 1.13.21) lets a holder of a Contributor-level account plant crafted content that executes as JavaScript in the browser of a more privileged user - typically an Editor or Administrator - who views the affected post, map, or template. The vulnerability is tracked as CVE-2026-78294 (CVSS 3.1 base 6.5, AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) and was reported through Patchstack; no public exploit code and no confirmed active exploitation were identified at time of analysis, so the practical risk is concentrated on multi-author blogs, community or membership sites where untrusted users can obtain Contributor accounts, and it does not affect default single-administrator installations or allow fully unauthenticated attackers to trigger it. Because the CVSS scope is Changed, a successful attack crosses the privilege boundary into the victim's session, where script execution can steal cookies or nonces, perform administrative actions in the victim's name, or pivot into larger site compromise.

RemediationAI

No vendor-released patched version is identified in the available data, which only confirms that versions up to and including 1.13.21 are affected; the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/geo-mashup/vulnerability/wordpress-geo-mashup-plugin-1-13-21-cross-site-scripting-xss-vulnerability is the primary source to monitor for a fixed release, and administrators should verify the plugin's current version before assuming they are covered. Until a fix is confirmed, the most effective action is to deactivate and - if maps are not essential to the site - remove Geo Mashup entirely, accepting the loss of its mapping functionality; where the plugin must stay live, restrict the Contributor role so that only fully trusted staff can hold it (or remove Contributor capabilities altogether on multi-author and community sites), which removes the injection prerequisite at the cost of blocking legitimate guest authorship. Additionally, treat any Contributor-authored post containing Geo Mashup output as untrusted: review and re-save or delete such content, and consider a web application firewall rule that blocks common script payload patterns in requests touching the plugin's endpoints, recognizing that WAF signatures are bypassable and provide detection rather than a true fix. Because exploitation requires an administrator or editor to view the poisoned content, operators can also temporarily limit privileged users to viewing only known-good posts, though this is disruptive and not a sustainable control.

Affected VersionsENISA

Geo Mashup n/a ≤1.13.21

Affected Packages

euvd geo_mashup no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is a classic CWE-79 improper neutralization of user-supplied input during page generation, occurring inside a third-party WordPress plugin rather than in WordPress core. Geo Mashup stores and renders geographic content - maps, markers, and associated post metadata - and the affected code path fails to correctly escape or sanitize data contributed by a low-privileged author before it is written into HTML attributes or markup that the browser later parses. WordPress by design removes the unfiltered_html capability from Contributors, so this is not a case of an author legitimately embedding markup; the plugin itself is the weak link that re-introduces executable content into a higher-privileged viewer's page. The CVSS vector confirms the boundary crossing: PR:L shows a valid low-privileged session is required to inject, UI:R shows a privileged user must be socially or casually induced to open the poisoned content, and S:C shows the resulting script acts with the victim's authority rather than the attacker's, which is why confidentiality, integrity, and availability impacts are each rated Low despite the modest base score.

Know when Geo Mashup gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 6.5 MEDIUM

Contributor account gives PR:L, admin must view the payload (UI:R), script runs cross-context (S:C) with limited C/I/A typical of XSS.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Contributor Cross Site Scripting (XSS) in Geo Mashup <= 1.13.21 versions.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
niche long-standing WordPress geo-mapping plugin, modest install base
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2018-14071 CRITICAL POC
9.8 Jul 16

The Geo Mashup plugin before 1.10.4 for WordPress has insufficient sanitization of post editor and other user input. Rat

CVE-2026-4060 HIGH POC
7.5 May 02

Time-based SQL injection in WordPress Geo Mashup plugin ≤1.13.18 allows unauthenticated remote attackers to extract sens

CVE-2026-48967 HIGH
8.5 Jun 17

SQL injection in the Geo Mashup WordPress plugin (versions <= 1.13.19) allows authenticated users with Subscriber-level

CVE-2026-66450 HIGH
8.1 Aug 13

Unauthenticated Local File Inclusion in the Geo Mashup WordPress plugin (all versions through 1.13.18) enables a remote,

CVE-2026-4061 HIGH
7.5 May 02

Time-based blind SQL injection in Geo Mashup WordPress plugin allows unauthenticated remote attackers to extract databas

CVE-2026-4062 HIGH
7.5 May 02

Time-based SQL injection in Geo Mashup WordPress plugin versions ≤1.13.18 allows unauthenticated remote attackers to ext

CVE-2026-66449 HIGH
7.1 Aug 13

Unauthenticated cross-site scripting in the Geo Mashup WordPress plugin (versions <= 1.13.18) allows remote attackers to

CVE-2026-97250 HIGH
7.1 Sep 30

Unauthenticated cross-site scripting in the WordPress Geo Mashup plugin affects all versions up to and including 1.13.21

CVE-2024-44008 MEDIUM
6.5 Sep 17

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dylan Kuhn Geo Mas

CVE-2026-27427 MEDIUM
6.5 May 26

Stored XSS in the Geo Mashup WordPress plugin (versions through 1.13.18) allows authenticated low-privileged users to pe

CVE-2026-6457 MEDIUM
6.5 May 02

Time-based blind SQL injection in Geo Mashup WordPress plugin versions up to 1.13.19 allows authenticated attackers with

CVE-2024-13362 MEDIUM
6.1 May 01

Multiple plugins and/or themes for WordPress are vulnerable to Reflected Cross-Site Scripting via the url parameter in v

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy