Skip to main content

CVE-2025-4100: Nautic Pages WordPress Plugin XSS Vulnerability

CVE-2025-4100 is a stored XSS vulnerability in Nautic Pages WordPress plugin affecting versions up to 2.0. Authenticated attackers can inject malicious scripts via shortcode attributes. This article covers technical details, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-4100 Overview

CVE-2025-4100 is a Stored Cross-Site Scripting (XSS) vulnerability in the Nautic Pages plugin for WordPress. The flaw affects all plugin versions up to and including 2.0. It resides in the handling of the np_marinetraffic_map shortcode, where user-supplied attributes are neither properly sanitized on input nor escaped on output. Authenticated users with contributor-level access or higher can inject arbitrary JavaScript that executes in the browser of any visitor who views the affected page. The weakness is categorized as CWE-79.

Critical Impact

Authenticated contributors can inject persistent JavaScript into WordPress pages, enabling session theft, administrative account takeover, and redirection of site visitors.

Affected Products

  • Nautic Pages plugin for WordPress — all versions up to and including 2.0
  • WordPress sites allowing contributor-level or higher accounts
  • Any page rendering the np_marinetraffic_map shortcode

Discovery Timeline

  • 2025-05-01 - CVE-2025-4100 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-4100

Vulnerability Analysis

The Nautic Pages plugin exposes the np_marinetraffic_map shortcode to WordPress authors and contributors. Shortcode attributes supplied by the user flow into the rendered page output without adequate sanitization or escaping. An authenticated attacker crafts a shortcode where one or more attribute values contain JavaScript payloads. When the resulting post or page is viewed, the injected script runs in the visitor's browser under the site's origin.

Because the payload is stored in the WordPress database and rendered on every page view, each visit triggers execution. Scope changes to the browser context, allowing the attacker to read cookies accessible to the page, perform actions as the viewing user, or pivot to administrator takeover if a privileged user loads the content.

Root Cause

The root cause is insufficient input sanitization and missing output escaping on attributes passed to the np_marinetraffic_map shortcode handler in nautic_pages.php. The plugin trusts attribute values and interpolates them into HTML output without applying WordPress escaping functions such as esc_attr() or esc_html(). Reference the plugin source for the affected code path.

Attack Vector

Exploitation requires an authenticated session with contributor-level privileges or higher. The attacker creates or edits a post that includes the np_marinetraffic_map shortcode with a malicious attribute value containing an event handler or <script> fragment. Once the content is published or previewed, any browser that renders the page executes the stored payload. See the Wordfence advisory for additional technical context.

// No verified public exploit code is available for CVE-2025-4100.
// The vulnerability is triggered by crafting a np_marinetraffic_map shortcode
// with attribute values containing JavaScript, then saving the post.

Detection Methods for CVE-2025-4100

Indicators of Compromise

  • Posts or pages containing np_marinetraffic_map shortcode attributes with <script>, onerror, onload, or javascript: substrings
  • Unexpected outbound HTTP requests from visitor browsers to attacker-controlled domains after loading plugin-rendered pages
  • Newly created contributor or author accounts that have authored posts using the vulnerable shortcode
  • Modifications to WordPress wp_posts records referencing the shortcode outside normal editorial workflows

Detection Strategies

  • Query the WordPress database for post_content entries containing np_marinetraffic_map and inspect attribute values for HTML or JavaScript syntax
  • Enable Content Security Policy (CSP) reporting to surface inline script execution originating from plugin-rendered pages
  • Review web server access logs for POST requests to wp-admin/post.php from contributor-level accounts that modify shortcode-bearing posts

Monitoring Recommendations

  • Alert on WordPress audit log events where non-administrator users publish or update posts containing the vulnerable shortcode
  • Monitor browser error telemetry and CSP violation reports for scripts executing on pages where the plugin is active
  • Track creation of new low-privilege accounts followed by rapid post-authoring activity

How to Mitigate CVE-2025-4100

Immediate Actions Required

  • Deactivate the Nautic Pages plugin on affected WordPress sites until a patched release is confirmed
  • Audit all contributor, author, and editor accounts and remove untrusted users
  • Search existing posts and pages for the np_marinetraffic_map shortcode and inspect attribute values for malicious content
  • Rotate administrator credentials and invalidate active sessions if evidence of exploitation exists

Patch Information

At the time of NVD publication, all versions of the Nautic Pages plugin up to and including 2.0 are affected. Site operators should monitor the WordPress plugin repository and the Wordfence advisory for an updated release that applies esc_attr() and related escaping to shortcode attributes.

Workarounds

  • Restrict contributor and author roles to trusted users only, and require editorial review before publishing posts that include shortcodes
  • Deploy a web application firewall rule that blocks requests saving np_marinetraffic_map shortcodes with HTML tags or JavaScript event handlers in attribute values
  • Enforce a strict Content Security Policy that disallows inline scripts on front-end pages served by WordPress
  • Remove the plugin entirely if the marine traffic map feature is not required
bash
# Example: locate posts containing the vulnerable shortcode via WP-CLI
wp db query "SELECT ID, post_title, post_author FROM wp_posts \
  WHERE post_content LIKE '%np_marinetraffic_map%' \
  AND post_status IN ('publish','draft','pending');"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.