Security readout for executives and security teams
Plain-English summary
CVE-2020-36759 affects the Woody code snippets WordPress plugin through version 2.3.9. An attacker could trick a logged-in administrator into clicking a crafted link or taking another action, causing snippets to be activated or deactivated without proper request validation. The impact is limited to integrity changes, but it matters on sites where snippets control business-critical behavior.
Executive priority
Treat this as a moderate-priority WordPress hygiene issue. It is not reported as actively exploited, but it can alter site behavior if an administrator is tricked. Prioritize externally managed or revenue-impacting WordPress sites using this plugin.
Technical view
The flaw is a CSRF issue caused by missing or incorrect nonce validation in runActions(). The reported effect is unauthorized activation or deactivation of snippets when an administrator is induced to submit a forged request. CVSS is 4.3, network reachable, low complexity, no privileges required, and user interaction required.
Likely exposure
Exposure is limited to WordPress sites running Woody Code Snippets, also listed as Insert PHP, CSS, JS, and Header/Footer Scripts, at version 2.3.9 or earlier. Sites without the plugin, or with a confirmed fixed vendor-supported version, are not indicated as affected by the provided sources.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires social engineering a site administrator, so risk depends on admin exposure and the operational importance of enabled snippets.
Researcher notes
The source bundle describes affected versions up to 2.3.9, while the affected metadata shown is sparse and internally unhelpful. Analysis should rely on the narrative description, Wordfence advisory, Nintechnet CSRF coverage, and the WordPress plugin changeset rather than inferring broader impact.
Mitigation direction
- Inventory WordPress sites for the Woody code snippets plugin and version.
- Update to a vendor-supported release newer than 2.3.9 when available.
- Check Wordfence and vendor guidance for the confirmed fixed version.
- Disable or remove the plugin where it is not operationally required.
- Review active snippets and disable nonessential snippets until remediation is complete.
Validation and detection
- Confirm whether any WordPress instance runs plugin version 2.3.9 or earlier.
- Review administrator activity for unexpected snippet activation or deactivation.
- Check whether snippet changes align with approved maintenance records.
- Verify the deployed plugin version against vendor or Wordfence advisory data.
- After updating, confirm snippet management actions use proper nonce validation.
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-36759 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/e573c0a4-d053-400b-828c-0d0eca880776?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?sfp_email=&sfph_mail=&reponame=&old=2368332%40insert-php&new=2368332%40insert-php&sfp_email=&sfph_mail=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.
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.