Skip to main content
Vulnerability Database/CVE-2026-95670

CVE-2026-95670: WordPress No External Links Plugin XSS

CVE-2026-95670 is a stored cross-site scripting flaw in the No External Links plugin for WordPress that lets unauthenticated attackers inject malicious scripts. This article covers technical details, affected versions, and mitigation.

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-2026-95670 Overview

CVE-2026-95670 is a Stored Cross-Site Scripting (XSS) vulnerability in the No External Links plugin for WordPress. The flaw affects all versions up to and including 5.2.0. It stems from insufficient input sanitization and output escaping in the /goto/{base64} redirect handler, which logs URLs that are later rendered in the admin log table. Unauthenticated attackers can inject arbitrary web scripts that execute when a user visits an affected page. Exploitation requires the administrator to have enabled the Link Encoding: Base64 option in plugin settings. The vulnerability is tracked under CWE-79.

Critical Impact

Unauthenticated attackers can inject persistent JavaScript that executes in administrator browsers, enabling session theft, account takeover, and backend compromise of affected WordPress sites.

Affected Products

  • WordPress No External Links plugin (mihdan-no-external-links) versions up to and including 5.2.0
  • WordPress sites with the Link Encoding: Base64 setting enabled
  • Any WordPress installation using the vulnerable plugin build on the /goto/{base64} redirect endpoint

Discovery Timeline

  • 2026-10-02 - CVE-2026-95670 published to NVD
  • 2026-10-03 - Last updated in NVD database

Technical Details for CVE-2026-95670

Vulnerability Analysis

The No External Links plugin rewrites outbound links through a redirector endpoint of the form /goto/{base64}. When the Link Encoding: Base64 option is enabled, the plugin decodes the base64 segment of the URL path and stores the resulting value in the plugin's redirect log. The decoded content is later rendered in the admin-facing log table without proper output escaping. An unauthenticated attacker can craft a request to /goto/{base64-payload} where the base64 segment decodes to attacker-controlled HTML or JavaScript. When an administrator subsequently views the plugin's log page, the stored payload executes in the context of the WordPress admin session. Successful exploitation can lead to session hijacking, creation of rogue administrator accounts, plugin or theme file modification, and pivoting to broader server compromise.

Root Cause

The root cause is a failure to sanitize decoded base64 input before storage and to escape stored URL values on output. The affected rendering logic resides in admin/LogTable.php around line 95, while the sources of the tainted data flow through public/Frontend.php at lines 451, 801, and 989. Neither esc_html() nor esc_url() is applied to the logged value before it is placed into the admin table markup, so attacker-supplied markup is rendered verbatim.

Attack Vector

An unauthenticated remote attacker sends a crafted HTTP request to the vulnerable site's /goto/{base64} endpoint. The base64 segment decodes to a JavaScript payload instead of a legitimate URL. The plugin writes the decoded value into its redirect log. When any administrator loads the plugin's log view in wp-admin, the browser executes the stored script with administrator privileges. See the Wordfence Vulnerability Analysis and the WordPress Plugin LogTable Code for the exact sink.

No verified public proof-of-concept code is available. The vulnerability mechanism is described in prose above.

Detection Methods for CVE-2026-95670

Indicators of Compromise

  • Requests to /goto/ endpoints with base64 segments that decode to HTML tags such as <script, <img, <svg, or onerror=.
  • Entries in the No External Links plugin log table containing raw HTML, JavaScript event handlers, or non-URL characters.
  • Unexpected creation of new WordPress administrator accounts or modifications to plugin and theme files shortly after admin visits to the plugin log page.

Detection Strategies

  • Review web server access logs for requests matching the pattern /goto/[A-Za-z0-9+/=]+ and base64-decode the segment to inspect for script content.
  • Query the WordPress database tables used by the plugin for log rows containing <, >, javascript:, or encoded script markers.
  • Compare the installed plugin version against 5.2.0 and flag any site running an equal or earlier release with Base64 link encoding enabled.

Monitoring Recommendations

  • Enable WordPress audit logging to capture administrator session activity, account creation, and plugin or theme file edits.
  • Deploy a Web Application Firewall (WAF) rule that inspects and decodes base64 segments in /goto/ paths and blocks payloads containing HTML or script tokens.
  • Alert on outbound administrator sessions originating from unexpected IP addresses, which may indicate session token theft.

How to Mitigate CVE-2026-95670

Immediate Actions Required

  • Update the No External Links plugin to a version later than 5.2.0 once the vendor publishes a fixed release.
  • Disable the Link Encoding: Base64 option in the plugin settings as an immediate workaround to remove the attack path.
  • Audit the plugin's redirect log and purge entries containing HTML or JavaScript content before any administrator accesses the log view.

Patch Information

A code update is tracked in the WordPress Plugin Changeset Update. Site operators should install the vendor-released fixed version from the WordPress plugin repository as soon as it becomes available and verify the plugin version number in wp-admin after the update.

Workarounds

  • Switch the plugin's link encoding mode away from Base64 to a non-decoded option until a patched release is installed.
  • Restrict access to the WordPress admin area by IP allowlisting so that only trusted operators can trigger the vulnerable log rendering path.
  • Deploy WAF rules that strip or block /goto/ requests whose decoded base64 payload contains characters outside the expected URL character set.
bash
# Example WAF rule concept (ModSecurity-style pseudocode)
SecRule REQUEST_URI "@rx ^/goto/([A-Za-z0-9+/=]+)$" \
  "id:1009567,phase:1,deny,status:403,\
   msg:'Potential CVE-2026-95670 XSS payload in /goto/ base64 segment',\
   chain"
  SecRule TX:1 "@rx (?i)(<script|<svg|onerror=|javascript:)"

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.