LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36755: Customizr <= 4.3.0 - Cross-Site Request Forgery Bypass

The Customizr theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.3.0. This is due to missing or incorrect nonce validation on the czr_fn_post_fields_save() function. This makes it possible for unauthenticated attackers to post fields 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

CVE-2020-36755 affects the Customizr WordPress theme up to version 4.3.0. It can let an attacker trick a logged-in administrator into submitting unintended theme-related field changes. This is not a server takeover issue in the provided sources, but it can alter site integrity if administrators are targeted.

Executive priority

Treat this as a routine but real website integrity issue. Prioritize remediation for public WordPress sites using Customizr, especially business-critical sites, but it does not warrant emergency response absent exploitation evidence.

Technical view

The issue is CWE-352 CSRF caused by missing or incorrect nonce validation in czr_fn_post_fields_save(). The CVSS 3.1 score is 4.3 with network attack vector, no privileges required, required user interaction, and low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites with the Customizr theme installed at version 4.3.0 or earlier, especially where administrators browse while authenticated. The source bundle has sparse affected-product metadata, so confirm theme presence and version directly.

Exploitation context

The sources describe a forged-request scenario requiring administrator interaction, such as clicking a link. KEV is false, and no cited source in the bundle establishes active exploitation in the wild.

Researcher notes

The key evidence is missing or incorrect nonce validation in czr_fn_post_fields_save(). The impact is constrained to integrity, with administrator interaction required. A WordPress Trac reference to Customizr 4.3.1 suggests reviewing that release, but confirm through vendor guidance.

Mitigation direction

  • Upgrade Customizr to a vendor-supported fixed release newer than 4.3.0.
  • Check Wordfence, Nintechnet, and vendor guidance for fixed-version confirmation.
  • Limit administrator browsing while logged into WordPress until upgraded.
  • Review admin accounts and recent theme-setting changes for unexpected modifications.

Validation and detection

  • Inventory WordPress sites for the Customizr theme.
  • Confirm whether installed Customizr versions are 4.3.0 or earlier.
  • Verify the installed release includes nonce validation for czr_fn_post_fields_save().
  • Review logs or change history for unexpected administrator-initiated field updates.
Prepared
Confidence
medium
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-36755 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-36755Attack 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
nikeoCustomizr0unaffected
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.