dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3231

HIGH · 7.2 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Checkout Field Editor (Checkout Manager) for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom radio and checkboxgroup field values submitted through the WooCommerce Block Checkout Store API in all versions up to, and including, 2.1.7. This is due to the `prepare_single_field_data()` method in `class-thwcfd-block-order-data.php` first escaping values with `esc_html()` then immediately reversing the escaping with `html_entity_decode()` for radio and checkboxgroup field types, combined with a permissive `wp_kses()` allowlist in `get_allowed_html()` that explicitly permits the `<select>` element with the `onchange` event handler attribute. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via the Store API checkout endpoint that execute when an administrator views the order details page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Checkout Field Editor for WooCommerce plugin has a stored XSS vulnerability where the `prepare_single_field_data()` method in `class-thwcfd-block-order-data.php` escapes values with `esc_html()` then immediately decodes them with `html_entity_decode()`, negating the protection. Combined with a permissive `wp_kses()` allowlist that permits `<select>` elements with `onchange` event handlers, unauthenticated attackers can inject malicious JavaScript via the WooCommerce Store API checkout endpoint that executes when administrators view order details.

MitigationUpdate the plugin to a version beyond 2.1.7 that properly handles escaping (removing the `html_entity_decode()` call) and removes dangerous event handler attributes like `onchange` from the `wp_kses()` allowlist.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and version
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Checkout Field Editor for WooCommerce' (or 'WooCommerce Checkout Field Editor'), and note the installed version number. Alternatively, inspect the plugin's main PHP file header for the 'Version' tag.
    Affected if The installed version is 2.1.7 or lower.
  2. Verify vulnerable file presence
    Locate the file class-thwcfd-block-order-data.php within the plugin directory, typically found under wp-content/plugins/checkout-field-editor-for-woocommerce/includes/blocks/ or similar path depending on plugin structure.
    Affected if The file exists in the plugin directory.
  3. Inspect vulnerable code pattern
    Open class-thwcfd-block-order-data.php and search within the prepare_single_field_data() method for the pattern where esc_html() is immediately followed by html_entity_decode(). Also examine the wp_kses() configuration to confirm <select> elements with onchange event handlers are permitted.
    Affected if The code contains esc_html() followed by html_entity_decode() in sequence, AND the wp_kses allowlist includes onchange attributes on <select> elements.
  4. Confirm WooCommerce Store API exposure
    Check if the WooCommerce Store API checkout endpoint is accessible and functional. This can be verified by reviewing WooCommerce > Settings > Advanced > REST API or by testing the /wp-json/wc/store/v1/checkout endpoint availability.
    Affected if The WooCommerce Store API checkout endpoint is enabled and accessible.
  5. Inspect recent orders for injected payloads
    In WordPress admin, go to WooCommerce > Orders and review recent orders, particularly looking at custom field data displayed in the order admin panel. Manually inspect order metadata database tables (wp_postmeta or wc_orders_meta) for any unexpected HTML, script tags, or event handler attributes in checkout field values.
    Affected if Any order contains malicious JavaScript or HTML in custom checkout fields, particularly in select element values with onchange handlers.

You are affected if the plugin version is 2.1.7 or lower AND the vulnerable code pattern (esc_html followed by html_entity_decode with permissive wp_kses) exists in the plugin, particularly if the WooCommerce Store API is active and orders contain suspicious field data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 2.1.7 that properly handles escaping (removing the `html_entity_decode()` call) and removes dangerous event handler attributes like `onchange` from the `wp_kses()` allowlist.

Recommended fix High confidence

Upgrade to Checkout Field Editor (Checkout Manager) for WooCommerce version 2.1.8 or later

  1. 1. Update the Checkout Field Editor (Checkout Manager) for WooCommerce plugin to version 2.1.8 or later.
  2. 2. After updating, verify the fix by checking that the `prepare_single_field_data()` method in `class-thwcfd-block-order-data.php` no longer reverses `esc_html()` escaping for radio and checkboxgroup field types.
  3. 3. Confirm that the `get_allowed_html()` function no longer permits the `<select>` element with `onchange` event handler attributes.
  4. 4. Test the WooCommerce Block Checkout Store API to ensure custom field submissions are properly sanitized and stored XSS is prevented.
  5. 5. As a best practice, clear any cached order data and verify that existing orders cannot be exploited through the stored payload.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3231 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data