Skip to main content

CVE-2025-47648: CWE-352 Cross-Site Request Forgery (CSRF) in axima Pays – WooCommerce Payment Gateway

High
VulnerabilityCVE-2025-47648cvecve-2025-47648cwe-352
Published: Wed May 07 2025 (05/07/2025, 14:20:43 UTC)
Source: CVE
Vendor/Project: axima
Product: Pays – WooCommerce Payment Gateway

Description

Cross-Site Request Forgery (CSRF) vulnerability in axima Pays – WooCommerce Payment Gateway allows Stored XSS. This issue affects Pays – WooCommerce Payment Gateway: from n/a through 2.6.

AI-Powered Analysis

AILast updated: 07/05/2025, 11:43:16 UTC

Technical Analysis

CVE-2025-47648 is a high-severity vulnerability classified as CWE-352 (Cross-Site Request Forgery, CSRF) affecting the axima Pays – WooCommerce Payment Gateway plugin, versions up to 2.6. This vulnerability allows an attacker to perform unauthorized actions on behalf of an authenticated user by exploiting the lack of proper CSRF protections in the payment gateway plugin. The vulnerability also enables Stored Cross-Site Scripting (XSS), which means malicious scripts can be injected and persist within the application, potentially affecting multiple users. The CVSS 3.1 base score of 7.1 indicates a high impact with network attack vector, low attack complexity, no privileges required, but user interaction is necessary. The scope is changed, meaning the vulnerability affects components beyond the initially vulnerable module. The impact includes partial loss of confidentiality, integrity, and availability, as attackers could manipulate payment processes or inject malicious scripts that execute in users’ browsers. The vulnerability is exploitable remotely without authentication but requires user interaction, such as clicking a crafted link or visiting a malicious website while authenticated to the WooCommerce site. No known exploits are currently reported in the wild, and no patches have been published yet. The plugin is widely used in e-commerce environments running WooCommerce on WordPress, which is popular in Europe for online retail. The combination of CSRF and Stored XSS increases the risk of session hijacking, unauthorized transactions, and broader compromise of user data and site integrity.

Potential Impact

For European organizations, especially e-commerce businesses using WooCommerce with the axima Pays payment gateway, this vulnerability poses a significant risk. Attackers could exploit CSRF to trick authenticated users into performing unintended payment actions, potentially causing financial loss or fraudulent transactions. The Stored XSS aspect can lead to theft of user credentials, session tokens, or injection of malicious payloads that affect customers and administrators alike. This can damage brand reputation, lead to regulatory non-compliance (e.g., GDPR violations due to data leakage), and disrupt business operations. Given the high adoption of WooCommerce in Europe’s SMB and mid-market e-commerce sectors, the threat could impact a broad range of retailers. Additionally, the vulnerability could be leveraged as a foothold for more advanced attacks, including supply chain compromises or lateral movement within affected networks.

Mitigation Recommendations

Organizations should immediately audit their WooCommerce installations to identify if the axima Pays – WooCommerce Payment Gateway plugin is in use and confirm the version. Until an official patch is released, mitigation steps include: 1) Implementing Web Application Firewall (WAF) rules to detect and block CSRF attack patterns and suspicious POST requests targeting the payment gateway endpoints. 2) Enforcing strict Content Security Policy (CSP) headers to mitigate the impact of Stored XSS by restricting script execution sources. 3) Educating users and administrators to avoid clicking on suspicious links while logged into the e-commerce site. 4) Temporarily disabling or replacing the vulnerable payment gateway plugin with an alternative solution that has proper CSRF protections. 5) Monitoring logs for unusual payment activity or unexpected parameter changes in payment requests. 6) Applying security headers such as SameSite cookies to reduce CSRF risks. 7) Preparing to deploy patches promptly once available from the vendor. These targeted mitigations go beyond generic advice by focusing on compensating controls and operational practices specific to this plugin and vulnerability type.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-05-07T10:45:13.129Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d981ac4522896dcbd9312

Added to database: 5/21/2025, 9:08:42 AM

Last enriched: 7/5/2025, 11:43:16 AM

Last updated: 7/27/2025, 6:32:38 PM

Views: 9

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