Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62942: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in tempranova WP Mapbox GL JS Maps

0
Medium
VulnerabilityCVE-2025-62942cvecve-2025-62942
Published: Mon Oct 27 2025 (10/27/2025, 01:34:05 UTC)
Source: CVE Database V5
Vendor/Project: tempranova
Product: WP Mapbox GL JS Maps

Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in tempranova WP Mapbox GL JS Maps wp-mapbox-gl-js allows Stored XSS.This issue affects WP Mapbox GL JS Maps: from n/a through <= 3.0.1.

AI-Powered Analysis

AILast updated: 10/27/2025, 02:24:53 UTC

Technical Analysis

CVE-2025-62942 is a stored Cross-site Scripting (XSS) vulnerability found in the tempranova WP Mapbox GL JS Maps WordPress plugin, affecting all versions up to and including 3.0.1. The vulnerability stems from improper neutralization of user-supplied input during the generation of web pages, allowing malicious scripts to be stored persistently within the plugin's data. When a victim visits a compromised page, the injected script executes in their browser context, potentially enabling attackers to steal authentication cookies, perform actions on behalf of the user, deface the website, or deliver malware. The vulnerability is particularly dangerous because it is stored XSS, meaning the malicious payload remains on the server and affects all users who access the infected content. No CVSS score has been assigned yet, and no public exploits have been reported, but the risk remains significant due to the widespread use of WordPress and the popularity of mapping plugins. The vulnerability affects organizations that use this plugin to embed Mapbox GL JS maps on their WordPress sites, which may include government, educational, and commercial entities. The lack of a patch link indicates that a fix may not yet be available, increasing the urgency for interim mitigations. Attackers do not require authentication to exploit this vulnerability if the plugin allows unauthenticated input, increasing the attack surface. Stored XSS vulnerabilities are often leveraged in targeted attacks or mass exploitation campaigns, making timely remediation critical.

Potential Impact

For European organizations, exploitation of this vulnerability could lead to significant confidentiality breaches through session hijacking, integrity issues via unauthorized content modification, and availability impacts if attackers deface or disrupt website functionality. Organizations that rely on WordPress sites with the WP Mapbox GL JS Maps plugin for public-facing services or internal portals could suffer reputational damage, loss of customer trust, and potential regulatory penalties under GDPR if personal data is compromised. The persistent nature of stored XSS increases the risk of widespread impact across all site visitors. Attackers could also use compromised sites as a vector to distribute malware or phishing content, further amplifying the threat. Critical infrastructure or government websites using this plugin could face targeted attacks aiming to disrupt services or gather intelligence. The absence of a patch at the time of disclosure means organizations must act quickly to implement mitigations to reduce exposure.

Mitigation Recommendations

1. Monitor the vendor’s official channels and Patchstack for the release of an official security update and apply it immediately upon availability. 2. In the interim, restrict or sanitize all user inputs that interact with the WP Mapbox GL JS Maps plugin, especially those that can be stored and rendered on web pages. 3. Employ a Web Application Firewall (WAF) with rules designed to detect and block XSS payloads targeting this plugin. 4. Conduct a thorough audit of all content generated via the plugin to identify and remove any injected malicious scripts. 5. Limit user permissions on WordPress to trusted users only, minimizing the risk of malicious content injection. 6. Educate site administrators and developers about the risks of stored XSS and safe coding practices. 7. Consider temporarily disabling the plugin if it is not critical to operations until a patch is available. 8. Implement Content Security Policy (CSP) headers to reduce the impact of potential XSS exploitation by restricting script execution sources.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-10-24T14:24:48.653Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68fed03223a7bbed324acc1d

Added to database: 10/27/2025, 1:51:46 AM

Last enriched: 10/27/2025, 2:24:53 AM

Last updated: 10/30/2025, 12:03:19 PM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats