LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36737: Import / Export Customizer Settings <= 1.0.3 - Cross-Site Request Forgery Bypass

The Import / Export Customizer Settings plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.3. This is due to missing or incorrect nonce validation on the astra_admin_errors() function. This makes it possible for unauthenticated attackers to display an import status 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 an administrator is tricked into clicking a malicious link, an unauthenticated attacker may cause the Import / Export Customizer Settings plugin to display an import status. The described impact is limited integrity change, with no confidentiality or availability impact stated.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not described as data theft or remote takeover, but administrator interaction can still cause unauthorized behavior. Remediate during the next normal WordPress maintenance window unless the plugin is broadly deployed.

Technical view

CVE-2020-36737 affects Import / Export Customizer Settings for WordPress through version 1.0.3. The astra_admin_errors() function lacked proper nonce validation, causing CWE-352 cross-site request forgery exposure. CVSS 3.1 is 4.3: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.

Likely exposure

Exposure is limited to WordPress sites running Import / Export Customizer Settings version 1.0.3 or earlier. Risk depends on an administrator being logged in and induced to perform an action. The provided sources do not establish exposure for other products.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The attack requires user interaction by a site administrator. Public references describe CSRF research across WordPress plugins, but no weaponized exploitation evidence is provided here.

Researcher notes

The core issue is missing or incorrect nonce validation in astra_admin_errors(). The stated outcome is displaying an import status, so impact appears narrow. Evidence is incomplete on fixed version labeling and real-world exploitation; avoid expanding scope beyond the named plugin and versions through 1.0.3.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and version.
  • Update beyond version 1.0.3 if vendor guidance confirms a fixed release.
  • If no fixed release is available, disable the plugin until vendor guidance is clear.
  • Restrict administrator browsing and reinforce anti-phishing controls.

Validation and detection

  • Check installed plugin version on each WordPress site.
  • Confirm whether astra_admin_errors() includes nonce validation in the installed code.
  • Review WordPress plugin changelog or Trac changeset for the nonce-validation fix.
  • Verify security scanners map findings specifically to CVE-2020-36737.
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-36737 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-36737Attack 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
brainstormforceImport / Export Customizer Settings0unaffected
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.