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-14165: CWE-352 Cross-Site Request Forgery (CSRF) in developerke Kirim.Email WooCommerce Integration

0
Medium
VulnerabilityCVE-2025-14165cvecve-2025-14165cwe-352
Published: Fri Dec 12 2025 (12/12/2025, 03:20:48 UTC)
Source: CVE Database V5
Vendor/Project: developerke
Product: Kirim.Email WooCommerce Integration

Description

The Kirim.Email WooCommerce Integration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.9. This is due to missing nonce validation on the plugin's settings page. This makes it possible for unauthenticated attackers to modify the plugin's API credentials and integration settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 12/12/2025, 04:03:50 UTC

Technical Analysis

CVE-2025-14165 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Kirim.Email WooCommerce Integration plugin for WordPress, affecting all versions up to and including 1.2.9. The root cause is the absence of nonce validation on the plugin's settings page, which is a critical security mechanism designed to verify that requests made to change settings originate from legitimate users and not from malicious third-party sites. Without this protection, an attacker can craft a malicious web request that, when executed by an authenticated administrator (e.g., by clicking a link), modifies the plugin's API credentials and integration settings without the administrator's consent. This vulnerability requires user interaction but no prior authentication, as the attacker exploits the administrator's active session. The impact primarily concerns the integrity of the plugin's configuration, potentially allowing attackers to redirect email communications, disrupt integration functionality, or facilitate further attacks such as phishing or data interception. The CVSS v3.1 score is 4.3 (medium severity), reflecting the network attack vector, low complexity, no privileges required, but requiring user interaction and limited impact on integrity only. No patches or known exploits are currently reported, but the vulnerability is publicly disclosed and should be addressed promptly to prevent exploitation.

Potential Impact

For European organizations, especially those operating e-commerce platforms using WooCommerce with the Kirim.Email integration, this vulnerability poses a risk of unauthorized modification of email integration settings. This could lead to misdirected transactional emails, loss of customer trust, or enable attackers to insert malicious content into communications. While the vulnerability does not directly compromise data confidentiality or availability, the integrity compromise can facilitate phishing campaigns or fraud, impacting brand reputation and customer relationships. Organizations with high reliance on email-based workflows or automated communications are particularly vulnerable. The risk is heightened in sectors with stringent data protection regulations like GDPR, where unauthorized changes could lead to compliance issues. Additionally, attackers could leverage this vulnerability as a foothold for broader attacks within the affected WordPress environment.

Mitigation Recommendations

1. Monitor for and apply official plugin updates from developerke that address nonce validation on the settings page as soon as they are released. 2. Until patches are available, restrict administrative access to trusted personnel only and limit exposure of the WordPress admin interface via IP whitelisting or VPN access. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious POST requests targeting the plugin’s settings endpoints. 4. Educate site administrators about the risks of clicking unsolicited links, especially when logged into administrative accounts. 5. Regularly audit plugin configurations and API credentials for unauthorized changes. 6. Consider disabling or replacing the Kirim.Email WooCommerce Integration plugin if immediate patching is not feasible, to reduce attack surface. 7. Employ security plugins that enforce nonce validation or add additional CSRF protections as a temporary measure.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-05T21:16:58.731Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693b918b650da22753edbe39

Added to database: 12/12/2025, 3:52:43 AM

Last enriched: 12/12/2025, 4:03:50 AM

Last updated: 12/15/2025, 4:10:32 AM

Views: 14

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