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-92990 Overview
CVE-2026-92990 affects the SendPress Newsletters WordPress plugin through version 1.26.1.20. The plugin protects a logging endpoint using a hardcoded token that is identical across every installation rather than a per-site secret. Unauthenticated attackers can use this shared token to access newsletter sending logs, exposing recipient email addresses. The issue is categorized as information disclosure [CWE-200] and can be exploited remotely without user interaction or authentication.
Critical Impact
Unauthenticated remote attackers can read newsletter sending logs and harvest recipient email addresses from any site running an affected version of SendPress Newsletters.
Affected Products
- SendPress Newsletters WordPress plugin, all versions up to and including 1.26.1.20
- WordPress sites that have installed and activated the affected plugin versions
- Any newsletter subscriber whose email address was recorded in the plugin's sending logs
Discovery Timeline
- 2026-10-09 - CVE-2026-92990 published to the National Vulnerability Database
- 2026-10-09 - Last updated in NVD database
Technical Details for CVE-2026-92990
Vulnerability Analysis
SendPress Newsletters exposes a logging endpoint intended for internal diagnostics. Access control relies on a static token value compiled into the plugin source. Because the same token ships with every installation of the plugin, it is effectively public knowledge once the plugin code is inspected.
An attacker who knows the token can issue unauthenticated HTTP requests to the endpoint on any site running the affected plugin. The response contains sending logs, including the email addresses of newsletter recipients. The disclosed data supports targeted phishing, spam campaigns, and subscriber-list enumeration against site owners and their audiences.
Root Cause
The root cause is the use of hardcoded credentials for an authorization check [CWE-200]. The plugin treats a shared compile-time secret as a per-site authentication factor. Any party that can read the plugin source, which is distributed publicly through the WordPress plugin repository, can derive the token and bypass the intended access boundary. A per-site secret generated at installation time would prevent cross-site reuse of the token.
Attack Vector
Exploitation requires only network access to the target WordPress site. The attacker crafts an HTTP request to the logging endpoint and includes the known static token. No credentials, user interaction, or elevated privileges are needed. The impact is limited to confidentiality: attackers can read logs but cannot modify data or affect availability through this specific flaw.
See the WPScan Vulnerability Report #595c6a6b for technical details on the vulnerable endpoint.
Detection Methods for CVE-2026-92990
Indicators of Compromise
- Unauthenticated HTTP GET or POST requests to the SendPress logging endpoint from unexpected source IPs
- Repeated access to plugin endpoints containing the hardcoded token parameter
- Unusual spikes in outbound bandwidth from /wp-content/plugins/sendpress/ paths
- Subscriber reports of targeted phishing messages following log exposure
Detection Strategies
- Review web server access logs for requests to SendPress plugin endpoints that include static token values
- Correlate requests across multiple WordPress sites in the same environment to identify scanners reusing the shared token
- Alert on anonymous requests that return large JSON or text responses from plugin endpoints
Monitoring Recommendations
- Enable verbose request logging on the WordPress reverse proxy or Web Application Firewall (WAF)
- Monitor the SendPress plugin version installed across all managed WordPress sites and flag versions at or below 1.26.1.20
- Track outbound email reputation and subscriber complaint rates to detect downstream abuse of leaked addresses
How to Mitigate CVE-2026-92990
Immediate Actions Required
- Update SendPress Newsletters to a version later than 1.26.1.20 as soon as the vendor releases a patched build
- Audit web server logs for prior access to the vulnerable logging endpoint and assess whether subscriber data was exfiltrated
- Notify subscribers if logs confirm exposure of their email addresses, in line with applicable privacy regulations
Patch Information
At the time of publication, no fixed version is referenced in the available advisories. Monitor the WPScan advisory and the plugin's WordPress.org listing for release notes that address the hardcoded token.
Workarounds
- Deactivate and remove the SendPress Newsletters plugin until a patched version is available
- Block external access to the vulnerable logging endpoint at the WAF or reverse proxy layer
- Restrict the plugin's logging path to known administrative IP ranges using web server access controls
# Example nginx rule to block external access to the SendPress logging endpoint
location ~* /wp-content/plugins/sendpress/.*log.* {
allow 10.0.0.0/8; # internal admin range
deny all;
return 403;
}
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

