Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-57977: CWE-352 Cross-Site Request Forgery (CSRF) in wpdesk Flexible PDF Invoices for WooCommerce & WordPress

0
High
VulnerabilityCVE-2025-57977cvecve-2025-57977cwe-352
Published: Mon Sep 22 2025 (09/22/2025, 18:24:32 UTC)
Source: CVE Database V5
Vendor/Project: wpdesk
Product: Flexible PDF Invoices for WooCommerce & WordPress

Description

Cross-Site Request Forgery (CSRF) vulnerability in wpdesk Flexible PDF Invoices for WooCommerce & WordPress allows Cross Site Request Forgery. This issue affects Flexible PDF Invoices for WooCommerce & WordPress: from n/a through 6.0.13.

AI-Powered Analysis

AILast updated: 09/30/2025, 00:34:53 UTC

Technical Analysis

CVE-2025-57977 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the wpdesk Flexible PDF Invoices plugin for WooCommerce and WordPress. This vulnerability affects all versions up to and including 6.0.13. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a malicious request to a web application without their consent or knowledge. In this case, the vulnerability allows an attacker to perform unauthorized actions on behalf of a logged-in user by exploiting the lack of proper anti-CSRF protections in the plugin. The CVSS 3.1 base score of 7.1 indicates a high severity level, with the vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H revealing that the attack can be launched remotely over the network without any privileges and requires user interaction (such as clicking a crafted link). The impact affects integrity and availability but not confidentiality. Specifically, the vulnerability can lead to unauthorized modification of invoice data or disruption of invoice generation processes, potentially causing denial of service or data tampering within the invoicing system. No known exploits are currently reported in the wild, and no patches have been linked yet, indicating that users should be vigilant and apply updates once available. The vulnerability is classified under CWE-352, which is a common web security weakness related to CSRF attacks.

Potential Impact

For European organizations, this vulnerability poses significant risks, especially for businesses relying on WooCommerce and WordPress with the wpdesk Flexible PDF Invoices plugin for their e-commerce invoicing and billing workflows. Successful exploitation could allow attackers to manipulate invoice data, disrupt invoice generation, or cause denial of service, leading to financial discrepancies, loss of customer trust, and operational interruptions. Given the widespread use of WooCommerce in European small and medium enterprises (SMEs), the impact could be substantial. Additionally, organizations subject to strict regulatory frameworks such as GDPR may face compliance issues if invoice data integrity is compromised. The attack requires user interaction but no authentication, meaning phishing or social engineering campaigns could be used to trick users into triggering the exploit. This elevates the risk in environments where employees or administrators have elevated privileges on WordPress sites. The lack of confidentiality impact reduces the risk of data leakage but does not mitigate the serious consequences of data integrity and availability loss in invoicing systems.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should: 1) Immediately monitor for updates or patches from wpdesk and apply them as soon as they become available. 2) Implement web application firewalls (WAFs) with rules to detect and block suspicious CSRF attack patterns targeting the plugin's endpoints. 3) Educate users and administrators about the risks of phishing and social engineering attacks that could trigger CSRF exploits, emphasizing cautious behavior with unsolicited links or emails. 4) Review and harden WordPress and WooCommerce security configurations, including limiting administrative access and enforcing least privilege principles. 5) Employ security plugins that add additional CSRF protections or nonce verification mechanisms to WordPress forms and actions. 6) Regularly audit and monitor logs for unusual invoice-related activities that could indicate exploitation attempts. 7) Consider isolating or segmenting the WordPress environment to limit the impact of potential compromises. These steps go beyond generic advice by focusing on proactive monitoring, user education, and layered defenses tailored to the specific plugin and attack vector.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-08-22T11:37:13.319Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d194c8a6a0abbafb7a3a30

Added to database: 9/22/2025, 6:26:16 PM

Last enriched: 9/30/2025, 12:34:53 AM

Last updated: 10/7/2025, 1:50:29 PM

Views: 1

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 are available only with a Pro account. Contact root@offseq.com for access.

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