Security readout for executives and security teams
Plain-English summary
A WordPress WooCommerce checkout-fields plugin allowed unauthenticated visitors to change plugin settings and store malicious script content. For stores using the vulnerable plugin, this could affect checkout integrity and expose customers or administrators to script execution. The CVE is high severity; the provided sources do not show current active exploitation.
Executive priority
Prioritize remediation for public WooCommerce stores, especially sites processing customer orders or payment-adjacent workflows. The issue requires no authentication and affects checkout-facing behavior, making business impact plausible even without confirmed current exploitation.
Technical view
CVE-2020-36731 affects Flexible Checkout Fields for WooCommerce through 2.3.1. The issue combines missing authorization checks in updateSettingsAction(), reachable through admin_init, with missing sanitization and escaping of stored settings. The result is unauthenticated arbitrary plugin settings update plus stored cross-site scripting.
Likely exposure
Exposure is limited to WordPress sites running the Flexible Checkout Fields for WooCommerce plugin at version 2.3.1 or earlier. WooCommerce stores are higher business-impact targets because checkout pages interact with customers and administrators.
Exploitation context
The CVE is not listed as KEV in the provided bundle. However, cited 2020 sources describe a zero-day fix and a site-takeover campaign exploiting multiple WordPress plugin zero-days. Treat historical exploitation risk as credible, but current exploitation is not established here.
Researcher notes
The supplied affected metadata is sparse and appears inconsistent with the description, which names versions up to 2.3.1. Use the CVE description and cited advisories for scope, and confirm exact fixed versions from vendor-controlled release guidance.
Mitigation direction
- Inventory WordPress sites for Flexible Checkout Fields for WooCommerce installations.
- Upgrade affected installations beyond version 2.3.1 following vendor guidance.
- If upgrade is unavailable, disable the plugin until vendor remediation is confirmed.
- Review plugin settings for unexpected checkout-field changes or injected content.
- Restrict WordPress administration access and monitor for unusual settings changes.
Validation and detection
- Confirm whether the plugin is installed and record its exact version.
- Compare installed versions against the vulnerable range: up to and including 2.3.1.
- Inspect checkout field settings for unexpected HTML, scripts, or unauthorized changes.
- Review web and WordPress logs for unauthenticated settings-modification activity.
- Verify stored checkout pages render without unexpected scripts after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36731 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/fd12a952-2e99-41f7-b74c-55c2b7d8deed?source=cveCVE reference
- https://blog.nintechnet.com/zero-day-vulnerability-fixed-in-wordpress-flexible-checkout-fields-for-woocommerce-plugin/CVE reference
- https://www.wordfence.com/blog/2020/02/site-takeover-campaign-exploits-multiple-zero-day-vulnerabilities/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.