CVE-2025-47648

7.1 HIGH

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in the axima Pays – WooCommerce Payment Gateway WordPress plugin allows attackers to perform stored cross-site scripting (XSS) attacks. This affects WordPress sites using the vulnerable payment gateway plugin. Attackers can inject malicious scripts that execute when administrators or users view affected pages.

💻 Affected Systems

Products:
  • axima Pays – WooCommerce Payment Gateway WordPress plugin
Versions: All versions up to and including 2.6
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with the vulnerable plugin activated. Requires the plugin to be installed and configured for WooCommerce payments.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could inject malicious JavaScript that steals administrator credentials, takes over the WordPress admin panel, or redirects users to phishing sites, potentially compromising the entire e-commerce site and customer data.

🟠

Likely Case

Attackers inject malicious scripts that steal session cookies or redirect users to malicious sites, leading to account compromise or financial fraud against customers.

🟢

If Mitigated

With proper CSRF protections and content security policies, the attack surface is reduced, though the vulnerability still exists in the codebase.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

CSRF vulnerabilities are typically easy to exploit with basic web development knowledge. The stored XSS component requires the attacker to trick an authenticated user into performing an action.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version after 2.6

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/axima-payment-gateway/vulnerability/wordpress-pays-woocommerce-payment-gateway-2-6-cross-site-request-forgery-csrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'axima Pays – WooCommerce Payment Gateway'. 4. Check if update is available. 5. Click 'Update Now' if update exists. 6. If no update appears, deactivate and remove the plugin immediately.

🔧 Temporary Workarounds

Disable vulnerable plugin

all

Temporarily disable the payment gateway plugin until patched

wp plugin deactivate axima-payment-gateway

Implement CSRF tokens

all

Add CSRF protection to WordPress forms if custom development is possible

🧯 If You Can't Patch

  • Disable the axima Pays plugin and use an alternative WooCommerce payment gateway
  • Implement strict Content Security Policy (CSP) headers to mitigate XSS impact

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for 'axima Pays – WooCommerce Payment Gateway' version 2.6 or earlier

Check Version:

wp plugin get axima-payment-gateway --field=version

Verify Fix Applied:

Verify plugin version is higher than 2.6 in WordPress admin plugins page

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to payment gateway endpoints
  • JavaScript injection attempts in form submissions
  • CSRF token validation failures

Network Indicators:

  • Unexpected cross-origin requests to payment endpoints
  • Malicious script loading from payment pages

SIEM Query:

source="wordpress.log" AND ("axima-payment" OR "pays-gateway") AND (POST OR "wp-admin")

🔗 References

📤 Share & Export