Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13515: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in danrajkumar Nouri.sh Newsletter

0
Medium
VulnerabilityCVE-2025-13515cvecve-2025-13515cwe-79
Published: Fri Dec 05 2025 (12/05/2025, 06:07:20 UTC)
Source: CVE Database V5
Vendor/Project: danrajkumar
Product: Nouri.sh Newsletter

Description

The Nouri.sh Newsletter plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `$_SERVER['PHP_SELF']` parameter in all versions up to, and including, 1.0.1.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 12/12/2025, 07:16:37 UTC

Technical Analysis

CVE-2025-13515 identifies a reflected Cross-Site Scripting (XSS) vulnerability in the Nouri.sh Newsletter plugin for WordPress, versions up to and including 1.0.1.3. The vulnerability stems from insufficient sanitization and escaping of the $_SERVER['PHP_SELF'] parameter during web page generation. This parameter is commonly used to reference the current script's filename, but if not properly neutralized, it can be manipulated by attackers to inject arbitrary JavaScript code. Because the vulnerability is reflected, the malicious payload is embedded in a crafted URL that, when clicked by a user, causes the injected script to execute in the context of the vulnerable website. The attack does not require authentication but does require user interaction (clicking a link). The CVSS 3.1 base score of 6.1 reflects a medium severity, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), scope changed (S:C), and impacts on confidentiality and integrity (C:L/I:L) but not availability (A:N). The scope change indicates the vulnerability affects resources beyond the vulnerable component, potentially impacting the broader site or user session. No public exploits are currently known, and no patches have been linked yet, suggesting the need for vigilance and proactive mitigation. The vulnerability falls under CWE-79, a common and well-understood class of injection flaws that can lead to session hijacking, defacement, or redirection to malicious sites.

Potential Impact

For European organizations, the impact of this vulnerability primarily concerns the confidentiality and integrity of user data and sessions. Attackers can exploit the reflected XSS to steal cookies, session tokens, or other sensitive information from users interacting with affected newsletter pages. This can lead to account compromise, unauthorized actions, or phishing attacks leveraging the trusted site context. Although availability is not directly impacted, successful exploitation can damage organizational reputation and user trust, especially for companies relying on newsletters for customer engagement. Public-facing WordPress sites using the Nouri.sh Newsletter plugin are at risk, particularly those with large subscriber bases or handling sensitive user information. The medium severity score suggests a moderate risk, but the ease of exploitation and lack of required privileges increase the threat level. European data protection regulations such as GDPR also impose obligations to protect user data, making exploitation potentially costly in terms of compliance and fines.

Mitigation Recommendations

1. Monitor for official patches or updates from the Nouri.sh Newsletter plugin vendor and apply them promptly once released. 2. Until patches are available, implement Web Application Firewall (WAF) rules to detect and block suspicious requests containing malicious payloads targeting the $_SERVER['PHP_SELF'] parameter. 3. Employ strict input validation and output encoding on all user-controllable inputs, especially URL parameters, to neutralize script injection attempts. 4. Configure Content Security Policy (CSP) headers to restrict the execution of inline scripts and loading of untrusted resources, mitigating the impact of XSS attacks. 5. Educate users and administrators about the risks of clicking unsolicited or suspicious links, particularly those related to newsletters or email campaigns. 6. Regularly audit WordPress plugins for vulnerabilities and consider alternative plugins with better security track records if timely patches are not forthcoming. 7. Use security plugins that can detect and block XSS attempts and monitor logs for unusual activity related to the newsletter pages.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-21T18:35:41.238Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69327c01f88dbe026c7c159f

Added to database: 12/5/2025, 6:30:25 AM

Last enriched: 12/12/2025, 7:16:37 AM

Last updated: 1/19/2026, 8:44:11 PM

Views: 86

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats