Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw could let an outside attacker change product metadata if they can trick an administrator into taking an action while logged in. The business risk is integrity impact to catalog content, not server takeover based on the provided sources.
Executive priority
Treat as a routine but real website integrity issue. Prioritize remediation for public commerce or catalog sites where unauthorized product changes could mislead customers or damage trust.
Technical view
CVE-2020-36743 is a CSRF issue in Product Catalog Simple up to and including 1.5.13. The source cites missing or incorrect nonce validation in implecode_save_products_meta(), allowing forged requests to update product meta when an administrator performs attacker-induced interaction.
Likely exposure
Exposure is limited to WordPress sites running Product Catalog Simple version 1.5.13 or earlier. Sites without this plugin, or with versions outside the cited vulnerable range, are not shown as affected in the provided bundle.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires user interaction from a site administrator, such as following a crafted link, and appears limited to product metadata changes.
Researcher notes
The evidence identifies CWE-352 and a specific nonce-validation weakness in implecode_save_products_meta(). The bundle does not provide exploit telemetry, payload details, or a definitive fixed version number, so validation should focus on version inventory and vendor-confirmed patches.
Mitigation direction
- Inventory WordPress sites for Product Catalog Simple installations.
- Update Product Catalog Simple beyond 1.5.13 where an official fixed version is available.
- Check Wordfence, WordPress plugin, and vendor guidance for exact fixed release details.
- Restrict administrative browsing and reinforce anti-phishing controls until remediated.
- Review recent product metadata changes for unauthorized or unexpected edits.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record installed plugin versions and flag versions 1.5.13 or earlier.
- Review the vulnerable function area for proper nonce validation after updating.
- Check WordPress admin audit logs for suspicious product metadata changes.
- Verify no public routes or forms expose unexpected product meta update behavior.
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-352: 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-36743 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/36e098fe-d1f9-4c8f-ae6b-222cbd5976b2?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset/2368377/post-type-x/trunk/core/includes/register-product.phpCVE 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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.