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-58800: CWE-352 Cross-Site Request Forgery (CSRF) in Steve Truman WP Email Template

0
Medium
VulnerabilityCVE-2025-58800cvecve-2025-58800cwe-352
Published: Fri Sep 05 2025 (09/05/2025, 13:45:07 UTC)
Source: CVE Database V5
Vendor/Project: Steve Truman
Product: WP Email Template

Description

Cross-Site Request Forgery (CSRF) vulnerability in Steve Truman WP Email Template allows Cross Site Request Forgery. This issue affects WP Email Template: from n/a through 2.8.3.

AI-Powered Analysis

AILast updated: 09/12/2025, 23:58:30 UTC

Technical Analysis

CVE-2025-58800 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Steve Truman WP Email Template WordPress plugin, affecting versions up to 2.8.3. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a forged request to a web application, causing unintended actions without the user's consent. In this case, the vulnerability allows an attacker to craft malicious requests that, when executed by an authenticated administrator or user with sufficient privileges, could alter the plugin's settings or email templates. The CVSS 3.1 base score of 4.3 reflects a medium severity level, indicating that while the vulnerability does not impact confidentiality or availability, it can affect the integrity of the plugin's configuration. The attack vector is network-based (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R), such as clicking a malicious link or visiting a crafted webpage. The vulnerability does not require authentication, but successful exploitation depends on the victim being logged into the WordPress admin interface. No known exploits are currently reported in the wild, and no official patches have been released at the time of publication. The vulnerability is categorized under CWE-352, which specifically addresses CSRF issues. Given the nature of the vulnerability, attackers could manipulate email templates or related settings, potentially enabling phishing campaigns or unauthorized email modifications that could deceive users or administrators.

Potential Impact

For European organizations using the Steve Truman WP Email Template plugin, this vulnerability poses a risk primarily to the integrity of their email communications managed through WordPress. Successful exploitation could allow attackers to modify email templates, potentially injecting malicious content or misleading information into emails sent to employees, customers, or partners. This can facilitate phishing attacks, social engineering, or reputational damage. Although the vulnerability does not directly compromise data confidentiality or system availability, the indirect effects on trust and communication integrity can be significant, especially for organizations relying heavily on email for internal and external communications. Additionally, organizations in regulated sectors such as finance, healthcare, or government may face compliance issues if unauthorized email modifications lead to data leakage or fraud. The requirement for user interaction and the need for the victim to be authenticated reduce the likelihood of widespread exploitation but do not eliminate risk, particularly in environments with many users or less stringent session management.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should take several specific steps beyond generic advice: 1) Immediately audit all WordPress installations for the presence of the Steve Truman WP Email Template plugin and identify versions in use. 2) Restrict administrative access to WordPress dashboards by implementing IP whitelisting or VPN access to reduce exposure to CSRF attacks. 3) Enforce strict session management policies, including short session timeouts and mandatory re-authentication for sensitive actions within the WordPress admin interface. 4) Educate users, especially administrators, about the risks of clicking on unsolicited links or visiting untrusted websites while logged into WordPress. 5) Monitor email templates and outgoing emails for unauthorized changes or suspicious content. 6) Implement Web Application Firewall (WAF) rules to detect and block CSRF attack patterns targeting the plugin’s endpoints. 7) Stay alert for official patches or updates from the plugin vendor and apply them promptly once available. 8) Consider disabling or replacing the plugin with alternatives that have stronger security postures if immediate patching is not possible.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-09-05T10:49:01.959Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68baeaa157c5b37b67a45fed

Added to database: 9/5/2025, 1:50:25 PM

Last enriched: 9/12/2025, 11:58:30 PM

Last updated: 10/16/2025, 8:58:50 PM

Views: 17

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats