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-15018: CWE-639 Authorization Bypass Through User-Controlled Key in djanym Optional Email

0
Critical
VulnerabilityCVE-2025-15018cvecve-2025-15018cwe-639
Published: Wed Jan 07 2026 (01/07/2026, 08:21:57 UTC)
Source: CVE Database V5
Vendor/Project: djanym
Product: Optional Email

Description

The Optional Email plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in all versions up to, and including, 1.3.11. This is due to the plugin not restricting its 'random_password' filter to registration contexts, allowing the filter to affect password reset key generation. This makes it possible for unauthenticated attackers to set a known password reset key when initiating a password reset, reset the password of any user including administrators, and gain access to their accounts.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:50:12 UTC

Technical Analysis

The djanym Optional Email plugin for WordPress, versions up to and including 1.3.11, contains a critical authorization bypass vulnerability identified as CVE-2025-15018. The root cause is the improper restriction of the 'random_password' filter, which is intended to be applied only during user registration but is erroneously applied during password reset key generation. This flaw allows unauthenticated attackers to specify a known password reset key when initiating a password reset request. Consequently, attackers can reset passwords for any user account, including those with administrative privileges, effectively enabling full account takeover without prior authentication or user interaction. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS v3.1 score of 9.8 reflects the ease of remote exploitation (no authentication or user interaction required), and the severe impact on confidentiality, integrity, and availability of affected WordPress sites. Although no public exploits have been reported yet, the critical nature of this flaw demands immediate attention from site administrators. The vulnerability affects all versions of the plugin up to 1.3.11, and no official patches have been linked at the time of reporting.

Potential Impact

This vulnerability poses a severe risk to organizations running WordPress sites with the djanym Optional Email plugin installed. Attackers can gain unauthorized administrative access, allowing them to manipulate site content, steal sensitive data, deploy malware, or disrupt services. The compromise of administrator accounts can lead to full site takeover, loss of customer trust, data breaches, and potential regulatory penalties. Since WordPress powers a significant portion of websites globally, including e-commerce, government, and enterprise sites, the impact can be widespread. The ease of exploitation without authentication or user interaction increases the likelihood of automated attacks and mass exploitation attempts once public exploits emerge. Organizations relying on this plugin face risks to their operational continuity, data confidentiality, and brand reputation.

Mitigation Recommendations

Immediate mitigation steps include disabling the Optional Email plugin until a secure patch is released. Administrators should monitor for updates from the vendor and apply patches promptly once available. As a temporary workaround, site owners can implement custom code to restrict the 'random_password' filter strictly to registration contexts, preventing its misuse during password resets. Additionally, enforcing multi-factor authentication (MFA) for all administrator accounts can reduce the risk of account takeover. Regularly auditing user accounts for unauthorized changes and monitoring logs for suspicious password reset activities are also recommended. Site owners should consider limiting password reset functionality through rate limiting or CAPTCHA challenges to hinder automated exploitation attempts. Finally, maintaining regular backups and having an incident response plan ready will help mitigate damage if exploitation occurs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-22T02:54:37.143Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695e1b30a55ed4ed998cb6a3

Added to database: 1/7/2026, 8:37:04 AM

Last enriched: 2/27/2026, 11:50:12 AM

Last updated: 3/25/2026, 1:33:43 AM

Views: 103

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses