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-13606: CWE-352 Cross-Site Request Forgery (CSRF) in smackcoders Export All Posts, Products, Orders, Refunds & Users

0
Medium
VulnerabilityCVE-2025-13606cvecve-2025-13606cwe-352
Published: Tue Dec 02 2025 (12/02/2025, 04:37:14 UTC)
Source: CVE Database V5
Vendor/Project: smackcoders
Product: Export All Posts, Products, Orders, Refunds & Users

Description

The Export All Posts, Products, Orders, Refunds & Users plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.19. This is due to missing or incorrect nonce validation on the `parseData` function. This makes it possible for unauthenticated attackers to export sensitive information including user data, email addresses, password hashes, and WooCommerce data to an attacker-controlled file path on the server 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/02/2025, 05:00:10 UTC

Technical Analysis

CVE-2025-13606 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WordPress plugin 'Export All Posts, Products, Orders, Refunds & Users' developed by smackcoders. The vulnerability exists in all versions up to and including 2.19 due to missing or incorrect nonce validation in the parseData function. Nonces in WordPress are security tokens used to verify that requests originate from legitimate users and prevent CSRF attacks. The absence or improper implementation of nonce validation allows an attacker to craft a malicious request that, when executed by an authenticated administrator (via clicking a link or visiting a malicious page), triggers the export of sensitive data. This data includes user personal information, email addresses, password hashes, and WooCommerce-related data such as orders and refunds. The exported data can be saved to a file path controlled by the attacker on the server, leading to potential data exfiltration. The vulnerability requires no prior authentication but does require user interaction from an administrator, making it a targeted but feasible attack vector. The CVSS v3.1 base score is 6.5 (medium severity), reflecting the high confidentiality impact but no impact on integrity or availability. No patches or exploit code are currently publicly available, and no known exploits in the wild have been reported. The vulnerability highlights the importance of proper nonce validation in WordPress plugins that handle sensitive data export functions.

Potential Impact

For European organizations, especially those operating e-commerce platforms using WooCommerce and the affected plugin, this vulnerability poses a significant risk of sensitive data leakage. Exposure of user data, including password hashes and personal information, can lead to identity theft, targeted phishing campaigns, and further compromise of user accounts. The ability to export order and refund data also risks financial information exposure and potential regulatory non-compliance under GDPR, which mandates strict protection of personal data. The confidentiality breach could damage organizational reputation and result in legal penalties. Since exploitation requires an administrator to be tricked into clicking a malicious link, social engineering attacks targeting administrative staff are a likely attack vector. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, the data confidentiality impact is severe enough to warrant urgent attention, especially for organizations handling large volumes of customer data.

Mitigation Recommendations

1. Immediately monitor and restrict administrative access to trusted personnel and educate administrators about phishing and social engineering risks to reduce the chance of clicking malicious links. 2. Until an official patch is released, consider disabling or uninstalling the vulnerable plugin to eliminate the attack surface. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious requests targeting the export functionality, especially those lacking valid nonces or originating from untrusted sources. 4. Review and harden WordPress security configurations, including enforcing strong administrator authentication methods such as multi-factor authentication (MFA). 5. Regularly audit plugin updates and subscribe to security advisories from smackcoders and WordPress security communities to apply patches promptly once available. 6. Conduct internal security assessments to verify that nonce validation is correctly implemented in custom or third-party plugins handling sensitive data exports. 7. Limit file system permissions on the server to prevent unauthorized writing of files to attacker-controlled paths. 8. Monitor server logs for unusual export activity or file creation events that could indicate exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-24T14:50:42.137Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692e6edbf8429d84f3bf2bb2

Added to database: 12/2/2025, 4:45:15 AM

Last enriched: 12/2/2025, 5:00:10 AM

Last updated: 12/4/2025, 4:57:18 PM

Views: 44

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