CVE-2026-3231

7.2 HIGH

📋 TL;DR

This vulnerability allows unauthenticated attackers to inject malicious scripts via WooCommerce checkout fields. When administrators view order details, these scripts execute, potentially compromising admin accounts. All WordPress sites using the Checkout Field Editor plugin up to version 2.1.7 are affected.

💻 Affected Systems

Products:
  • Checkout Field Editor (Checkout Manager) for WooCommerce WordPress plugin
Versions: All versions up to and including 2.1.7
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WooCommerce with block-based checkout enabled. Classic checkout may not be affected.

⚠️ 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 gain administrative access to WordPress, install backdoors, steal sensitive customer data, or deface the website.

🟠

Likely Case

Attackers hijack admin sessions to modify site content, redirect users, or install cryptocurrency miners.

🟢

If Mitigated

With proper input validation and output escaping, script execution is prevented, limiting impact to data integrity issues.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

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

Exploitation requires submitting malicious payload through the Store API checkout endpoint, which is publicly accessible.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.1.8 or later

Vendor Advisory: https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3478914%40woo-checkout-field-editor-pro%2Ftrunk&old=3454287%40woo-checkout-field-editor-pro%2Ftrunk&sfp_email=&sfph_mail=#file1

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Checkout Field Editor for WooCommerce'. 4. Click 'Update Now' if available. 5. Alternatively, download version 2.1.8+ from WordPress.org and manually update.

🔧 Temporary Workarounds

Disable plugin temporarily

all

Deactivate the vulnerable plugin until patched.

wp plugin deactivate woo-checkout-field-editor-pro

Switch to classic checkout

all

Use WooCommerce's classic checkout instead of block-based checkout.

🧯 If You Can't Patch

  • Restrict access to the WordPress admin panel to trusted IP addresses only.
  • Implement a Web Application Firewall (WAF) with XSS protection rules.

🔍 How to Verify

Check if Vulnerable:

Check plugin version in WordPress admin under Plugins > Installed Plugins. If version is 2.1.7 or lower, you are vulnerable.

Check Version:

wp plugin get woo-checkout-field-editor-pro --field=version

Verify Fix Applied:

After updating, verify plugin version is 2.1.8 or higher. Test checkout functionality to ensure no regression.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /wp-json/wc/store/checkout endpoint with script-like payloads in field values.
  • Admin user sessions with unexpected behavior after viewing order details.

Network Indicators:

  • HTTP requests containing <select onchange=...> patterns in checkout data.

SIEM Query:

source="wordpress.log" AND "POST /wp-json/wc/store/checkout" AND ("onchange=" OR "<select")

🔗 References

📤 Share & Export