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-28923: Cross-Site Request Forgery (CSRF) in philippe No Disposable Email

0
Unknown
VulnerabilityCVE-2025-28923cvecve-2025-28923
Published: Tue Mar 11 2025 (03/11/2025, 21:01:04 UTC)
Source: CVE Database V5
Vendor/Project: philippe
Product: No Disposable Email

Description

Cross-Site Request Forgery (CSRF) vulnerability in philippe No Disposable Email no-disposable-email allows Stored XSS.This issue affects No Disposable Email: from n/a through <= 2.5.1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/01/2026, 23:41:06 UTC

Technical Analysis

CVE-2025-28923 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the 'No Disposable Email' plugin developed by philippe, specifically affecting versions up to and including 2.5.1. The vulnerability enables an attacker to trick an authenticated user into submitting unwanted requests to the vulnerable web application, leveraging the user's credentials and session context. This CSRF flaw is compounded by the presence of Stored Cross-Site Scripting (XSS), where malicious scripts injected by the attacker are persistently stored on the server and executed in the context of other users' browsers. The combination of CSRF and Stored XSS significantly increases the attack surface, allowing attackers to perform unauthorized actions, steal sensitive information such as session cookies, or manipulate application data. The plugin is typically used to prevent disposable or temporary email addresses during user registration or form submissions, making it a common component in web applications that require email validation. No public exploits have been reported yet, but the vulnerability is published and should be considered exploitable given the nature of CSRF and Stored XSS attacks. The lack of a CVSS score indicates that the severity must be assessed based on the potential impact and exploitability. The vulnerability does not require user interaction beyond the victim being authenticated and visiting a malicious page, which lowers the barrier for exploitation. The absence of patch links suggests that remediation may require vendor updates or manual mitigation steps.

Potential Impact

The impact of CVE-2025-28923 is significant for organizations using the 'No Disposable Email' plugin in their web applications. Exploitation can lead to unauthorized actions performed under the guise of legitimate users, including changes to user data, unauthorized transactions, or privilege escalation. The Stored XSS component can result in persistent malicious code execution, enabling attackers to hijack user sessions, steal credentials, or deliver malware. This can compromise the confidentiality, integrity, and availability of affected systems and user data. Organizations may face data breaches, reputational damage, and regulatory penalties if sensitive information is exposed. Since the vulnerability affects a plugin commonly used in web forms and user registration processes, a wide range of industries including e-commerce, SaaS providers, and online communities could be impacted. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability details are public. The ease of exploitation, requiring only an authenticated user and no complex prerequisites, increases the likelihood of successful attacks in targeted environments.

Mitigation Recommendations

To mitigate CVE-2025-28923, organizations should prioritize updating the 'No Disposable Email' plugin to a version where this vulnerability is patched once available. In the absence of an official patch, implement strict anti-CSRF protections such as synchronizer tokens or double-submit cookies to ensure that all state-changing requests are validated. Review and harden input validation and output encoding mechanisms to prevent Stored XSS, including sanitizing all user-supplied data before storage and rendering. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. Conduct thorough security testing on web forms and user input handling components. Additionally, monitor web application logs for unusual activities that may indicate exploitation attempts. Educate users about phishing and social engineering tactics that could be used to trigger CSRF attacks. Finally, consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block CSRF and XSS attack patterns targeting this plugin.

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
Patchstack
Date Reserved
2025-03-11T08:09:40.253Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd72eee6bfc5ba1deef562

Added to database: 4/1/2026, 7:33:02 PM

Last enriched: 4/1/2026, 11:41:06 PM

Last updated: 4/6/2026, 10:59:17 AM

Views: 4

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