CVE-2025-49353
7.1Marcin Kijak · Noindex by Path
A Cross-Site Request Forgery (CSRF) vulnerability in the Noindex by Path WordPress plugin allows an unauthenticated attacker to inject malicious scripts, resulting in Stored Cross-Site Scripting (XSS).
Executive summary
The Noindex by Path plugin is vulnerable to a CSRF-based Stored XSS attack that could allow unauthenticated attackers to execute arbitrary scripts in the context of an administrator session.
Vulnerability
The plugin fails to implement adequate CSRF protection, enabling an attacker to trick a logged-in user into executing unintended actions that lead to the persistent injection of malicious scripts. This vulnerability is triggered by an unauthenticated remote attacker who induces a victim to perform a state-changing action.
Business impact
The exploitation of this vulnerability poses a significant risk to organizational security by allowing the execution of unauthorized scripts within the browser of authenticated users. A successful attack could lead to session hijacking, unauthorized configuration changes, or the exfiltration of sensitive site data. With a CVSS score of 7.1, this represents a High severity risk that requires immediate prioritization.
Remediation
Immediate Action: There is currently no confirmed patch available; administrators should immediately disable or uninstall the Noindex by Path plugin until a secure version is released.
Proactive Monitoring: Monitor web application logs for suspicious requests originating from external sources that target plugin-specific settings or administrative endpoints.
Compensating Controls: Deploy a Web Application Firewall (WAF) with robust CSRF protection rules to inspect incoming traffic and block requests that lack proper anti-forgery tokens.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Given the High severity of this vulnerability and the potential for persistent XSS execution, organizations must treat this issue with urgency. Because a patch is not currently available, the most effective mitigation is the immediate removal of the affected software from the environment to prevent potential compromise.
Sources
Originally found and disclosed by Skalucy | Patchstack Bug Bounty Program, per the CVE Program record.