CVE-2026-2025: CWE-200 Information Exposure in Mail Mint
CVE-2026-2025 is an information exposure vulnerability in the Mail Mint WordPress plugin versions before 1. 19. 5. The flaw exists because one of the plugin's REST API endpoints lacks proper authorization, allowing unauthenticated users to access it. Exploiting this vulnerability enables attackers to retrieve email addresses of users registered on the affected WordPress site. Although no known exploits are currently in the wild, the exposure of user email addresses can facilitate phishing, spam campaigns, or further targeted attacks. The vulnerability does not require authentication or user interaction, increasing its risk. Organizations running vulnerable versions of Mail Mint are at risk of user data leakage. Mitigation involves updating the plugin to version 1. 19.
AI Analysis
Technical Summary
CVE-2026-2025 is a vulnerability classified under CWE-200 (Information Exposure) affecting the Mail Mint WordPress plugin prior to version 1.19.5. The root cause is the absence of authorization checks on one of the plugin's REST API endpoints. This flaw allows unauthenticated attackers to invoke the endpoint and retrieve email addresses of users registered on the WordPress site. The exposed data primarily includes user email addresses, which are sensitive personal information. The vulnerability arises because the REST API endpoint was designed without proper access control, violating the principle of least privilege. Since WordPress powers a significant portion of websites globally, and Mail Mint is a popular plugin for managing email subscriptions and newsletters, many sites could be vulnerable if they have not updated the plugin. The vulnerability does not require any authentication or user interaction, making it trivially exploitable by remote attackers. No CVSS score has been assigned yet, and no public exploits have been reported. However, the exposure of user emails can lead to secondary attacks such as phishing, spam, or social engineering, potentially compromising user privacy and trust. The vulnerability was publicly disclosed in March 2026, with the patch version 1.19.5 addressing the issue by implementing proper authorization checks on the REST API endpoint.
Potential Impact
The primary impact of this vulnerability is the unauthorized disclosure of user email addresses, which compromises confidentiality. This exposure can facilitate phishing attacks, spam distribution, and social engineering campaigns targeting users of the affected WordPress sites. Organizations relying on Mail Mint for email subscription management risk reputational damage and loss of user trust if their users' email addresses are leaked. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of successful phishing or targeted attacks could lead to broader security incidents, including credential theft or malware infections. The ease of exploitation—requiring no authentication or user interaction—means attackers can automate the harvesting of email addresses at scale. This increases the likelihood of widespread abuse, especially for high-profile blogs or websites with large user bases. The lack of known exploits in the wild currently limits immediate risk, but the vulnerability remains a significant concern until patched.
Mitigation Recommendations
To mitigate this vulnerability, organizations should promptly update the Mail Mint plugin to version 1.19.5 or later once it is released, as this version includes the necessary authorization checks on the REST API endpoint. Until the patch is applied, administrators can restrict access to the vulnerable REST API endpoint by implementing web application firewall (WAF) rules that block unauthenticated requests to the specific API path. Additionally, limiting REST API access to authenticated users only or IP whitelisting trusted sources can reduce exposure. Site owners should audit their WordPress plugins regularly to ensure they are up to date and monitor logs for unusual API access patterns. Educating users about phishing risks and encouraging the use of multi-factor authentication can help mitigate the impact of any leaked email addresses. Finally, disabling unused REST API endpoints or restricting REST API access globally via plugin or server configuration can provide an additional security layer.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, India, Brazil, France, Japan, Netherlands
CVE-2026-2025: CWE-200 Information Exposure in Mail Mint
Description
CVE-2026-2025 is an information exposure vulnerability in the Mail Mint WordPress plugin versions before 1. 19. 5. The flaw exists because one of the plugin's REST API endpoints lacks proper authorization, allowing unauthenticated users to access it. Exploiting this vulnerability enables attackers to retrieve email addresses of users registered on the affected WordPress site. Although no known exploits are currently in the wild, the exposure of user email addresses can facilitate phishing, spam campaigns, or further targeted attacks. The vulnerability does not require authentication or user interaction, increasing its risk. Organizations running vulnerable versions of Mail Mint are at risk of user data leakage. Mitigation involves updating the plugin to version 1. 19.
AI-Powered Analysis
Technical Analysis
CVE-2026-2025 is a vulnerability classified under CWE-200 (Information Exposure) affecting the Mail Mint WordPress plugin prior to version 1.19.5. The root cause is the absence of authorization checks on one of the plugin's REST API endpoints. This flaw allows unauthenticated attackers to invoke the endpoint and retrieve email addresses of users registered on the WordPress site. The exposed data primarily includes user email addresses, which are sensitive personal information. The vulnerability arises because the REST API endpoint was designed without proper access control, violating the principle of least privilege. Since WordPress powers a significant portion of websites globally, and Mail Mint is a popular plugin for managing email subscriptions and newsletters, many sites could be vulnerable if they have not updated the plugin. The vulnerability does not require any authentication or user interaction, making it trivially exploitable by remote attackers. No CVSS score has been assigned yet, and no public exploits have been reported. However, the exposure of user emails can lead to secondary attacks such as phishing, spam, or social engineering, potentially compromising user privacy and trust. The vulnerability was publicly disclosed in March 2026, with the patch version 1.19.5 addressing the issue by implementing proper authorization checks on the REST API endpoint.
Potential Impact
The primary impact of this vulnerability is the unauthorized disclosure of user email addresses, which compromises confidentiality. This exposure can facilitate phishing attacks, spam distribution, and social engineering campaigns targeting users of the affected WordPress sites. Organizations relying on Mail Mint for email subscription management risk reputational damage and loss of user trust if their users' email addresses are leaked. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of successful phishing or targeted attacks could lead to broader security incidents, including credential theft or malware infections. The ease of exploitation—requiring no authentication or user interaction—means attackers can automate the harvesting of email addresses at scale. This increases the likelihood of widespread abuse, especially for high-profile blogs or websites with large user bases. The lack of known exploits in the wild currently limits immediate risk, but the vulnerability remains a significant concern until patched.
Mitigation Recommendations
To mitigate this vulnerability, organizations should promptly update the Mail Mint plugin to version 1.19.5 or later once it is released, as this version includes the necessary authorization checks on the REST API endpoint. Until the patch is applied, administrators can restrict access to the vulnerable REST API endpoint by implementing web application firewall (WAF) rules that block unauthenticated requests to the specific API path. Additionally, limiting REST API access to authenticated users only or IP whitelisting trusted sources can reduce exposure. Site owners should audit their WordPress plugins regularly to ensure they are up to date and monitor logs for unusual API access patterns. Educating users about phishing risks and encouraging the use of multi-factor authentication can help mitigate the impact of any leaked email addresses. Finally, disabling unused REST API endpoints or restricting REST API access globally via plugin or server configuration can provide an additional security layer.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WPScan
- Date Reserved
- 2026-02-05T20:41:56.158Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69a7ceacd1a09e29cb03bd89
Added to database: 3/4/2026, 6:18:20 AM
Last enriched: 3/4/2026, 6:32:40 AM
Last updated: 3/4/2026, 7:27:58 AM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-28770: CWE-91: XML Injection (aka Blind XPath Injection) in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver Web management interface
MediumCVE-2026-28769: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver Web management interface
MediumCVE-2026-2732: CWE-862 Missing Authorization in shortpixel Enable Media Replace
MediumCVE-2026-2363: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in cbutlerjr WP-Members Membership Plugin
MediumCVE-2026-27012: CWE-306: Missing Authentication for Critical Function in devcode-it openstamanager
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.