LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36740: Radio Buttons for Taxonomies <= 2.0.5 - Cross-Site Request Forgery Bypass

The Radio Buttons for Taxonomies plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.5. This is due to missing or incorrect nonce validation on the save_single_term() function. This makes it possible for unauthenticated attackers to save terms via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a WordPress plugin CSRF issue. If a site uses Radio Buttons for Taxonomies version 2.0.5 or earlier, an attacker could trick an authenticated administrator into causing taxonomy terms to be saved without intending it. The documented impact is limited integrity change, not data theft or service outage.

Executive priority

Treat this as a moderate cleanup item for WordPress estates. It is not documented as actively exploited, but affected sites allow unauthorized content-structure changes if an administrator is socially engineered. Prioritize sites with many administrators or sensitive taxonomy-driven publishing workflows.

Technical view

CVE-2020-36740 is CWE-352 in Radio Buttons for Taxonomies. Sources attribute it to missing or incorrect nonce validation in save_single_term(). A forged request can save terms if an unauthenticated attacker persuades an administrator to perform an action. CVSS 3.1 is 4.3 with required user interaction and low integrity impact.

Likely exposure

Exposure is limited to WordPress installations running Radio Buttons for Taxonomies up to and including 2.0.5. Sites without the plugin, or not using affected versions, are not indicated as exposed by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires administrator interaction, such as being tricked into clicking a link, while the vulnerable plugin is present. The documented outcome is unauthorized saving of terms.

Researcher notes

The affected function named in the source bundle is save_single_term(). The vulnerability class is CSRF caused by missing or incorrect nonce validation. Evidence in the bundle supports affected versions through 2.0.5, CVSS 4.3, and no KEV listing; it does not prove active exploitation.

Mitigation direction

  • Inventory WordPress sites for Radio Buttons for Taxonomies installations.
  • If version is 2.0.5 or earlier, update using official plugin guidance.
  • Review vendor changelog or WordPress Trac changeset for the nonce-validation fix.
  • Restrict administrator browsing and avoid acting on untrusted links while logged in.
  • Monitor taxonomy or term changes for unexpected administrator-attributed updates.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record installed plugin versions and flag 2.0.5 or earlier.
  • Verify administrative term-saving actions require valid nonce protection after updating.
  • Review site logs or audit trails for unexpected taxonomy term changes.
  • Confirm no affected version remains in production or staging.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2020-36740 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2020-36740Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
helgathevikingRadio Buttons for Taxonomies0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.