CVE-2026-130892 in Newsletter Plugin
Summary
by MITRE • 11/21/2026
The Newsletter WordPress plugin before 9.4.0 does not properly validate the destination of the redirect performed when a subscriber changes their list membership from a newsletter link, checking only that it begins with the site's URL, allowing unauthenticated attackers to redirect users to external sites whose address starts with the site's URL.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in versions of the Newsletter WordPress plugin prior to 9.4.0 constitutes an Open Redirect flaw rooted in insufficient input validation within the subscription management workflow. This security defect specifically affects the mechanism that handles subscriber list membership changes initiated through newsletter links. When a user interacts with such a link, the application performs a redirect operation to update their status or preferences. The core technical failure lies in the logic used to validate the destination URL provided for this redirection. Instead of performing a comprehensive check against an allowlist of permitted domains or verifying that the target is strictly internal and safe, the plugin employs a simplistic string prefix check. It verifies only whether the redirect destination begins with the site's own base URL. This approach fails to account for common evasion techniques used by attackers, such as utilizing path traversal sequences like double slashes (//) followed by an external domain, or exploiting protocol-relative URLs that bypass standard host validation checks. Consequently, this logic flaw allows unauthenticated actors to craft malicious links that appear legitimate at a superficial glance but ultimately direct users away from the trusted WordPress site to arbitrary external destinations controlled by the attacker.
From an operational perspective, this vulnerability poses significant risks related to phishing and credential harvesting. Because the redirect originates from a domain that is already trusted by the user's browser and security software, it carries a high degree of credibility. Attackers can leverage this trust to host malicious landing pages on external servers while making them appear as if they are part of the legitimate website. Users clicking these links may be deceived into entering sensitive information such as login credentials, personal identifiable data, or financial details on fraudulent sites that mimic the appearance of the original WordPress site. Furthermore, this vulnerability can facilitate drive-by download attacks where users are redirected to pages hosting malicious payloads designed to exploit browser vulnerabilities or install malware upon their devices. The lack of authentication requirements means that any internet user with knowledge of the target website's URL structure can construct and distribute these malicious links via email, social media, or other communication channels without needing prior access credentials.
In terms of industry standard classifications, this vulnerability aligns closely with CWE-601, which describes Open Redirect to an Untrusted Site in a Web Application. The flaw represents a failure in the application's ability to properly validate user-supplied input before using it for redirection logic. Additionally, from a tactical standpoint within the MITRE ATT&CK framework, this vulnerability supports techniques associated with Initial Access and Credential Harvesting. Specifically, it facilitates Phishing via Spearphishing Link (T1566.002) by allowing attackers to disguise malicious links as legitimate communications from trusted sources. It also relates to Obfuscated Files or Information (T1027) when the redirect URL is encoded or obfuscated to evade basic security filters, although in this specific case, the primary issue remains the insufficient validation logic rather than complex obfuscation techniques. The exploitation of this flaw does not require any special privileges, making it a low-barrier entry point for adversaries looking to compromise user accounts or distribute malware within an organization that relies on this plugin for communication.
Mitigation strategies must address both immediate remediation and long-term security hygiene. The most effective solution is to upgrade the Newsletter WordPress plugin to version 9.4.0 or later, where the developers have presumably implemented stricter validation mechanisms such as allowlisting specific internal paths or using robust URL parsing libraries that correctly identify hostnames regardless of prefix tricks. For organizations unable to patch immediately due to compatibility constraints, temporary mitigations include implementing a Web Application Firewall (WAF) rule set designed to detect and block requests containing suspicious redirect parameters, particularly those involving double slashes followed by external domains. Additionally, administrators should enforce strict Content Security Policy headers that restrict the sources from which scripts can be executed or where redirects are permitted, although this may require careful tuning to avoid breaking legitimate site functionality. Regular security audits of third-party plugins are essential to identify similar validation flaws in other components, ensuring that all user-controlled inputs used for navigation or redirection undergo rigorous sanitization and verification against a strict allowlist rather than relying on fragile prefix checks.