CVE-2026-95670 mihdan CVE debrief

Who should care

WordPress administrators and defenders should be aware of this vulnerability and assess their exposure, especially if the 'Link Encoding: Base64' option is enabled in the plugin settings.

Why it matters

The CVE-2026-95670 vulnerability in the No External Links plugin for WordPress allows unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if the 'Link Encoding: Base64' option is enabled in the plugin settings.

• Defenders need to verify if the No External Links plugin is installed and enabled on WordPress systems.
• Assess the impact of this vulnerability on WordPress systems and prioritize remediation.
• Consider implementing additional security measures to prevent cross-site scripting attacks.
• Verify if the 'Link Encoding: Base64' option is enabled in the plugin settings.

Technical summary

The No External Links plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Log URL. This issue affects all versions up to, and including, 5.2.0 due to insufficient input sanitization and output escaping. The vulnerability allows unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable when the administrator has enabled the 'Link Encoding: Base64' option in the plugin settings.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if the 'Link Encoding: Base64' option is enabled in the plugin settings.

Recommended defensive actions

• Verify if the No External Links plugin is installed and enabled on WordPress systems
• Check if the 'Link Encoding: Base64' option is enabled in the plugin settings
• Assess the impact of this vulnerability on WordPress systems and prioritize remediation
• Consider implementing additional security measures to prevent cross-site scripting attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 7.2 and HIGH severity. The vulnerability allows unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.