LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36711: Avada <= 6.2.2 - Authenticated (Contributor+) Cross-Site Scripting

The Avada theme for WordPress is vulnerable to Stored Cross-Site Scripting via the update_layout function in versions up to, and including, 6.2.3 due to insufficient input sanitization and output escaping. This makes it possible for contributor-level attackers, and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-36711 is a stored cross-site scripting issue in the Avada WordPress theme. A contributor-level user or higher could save malicious script content that runs when someone views the affected page. This can expose users to account or content manipulation risk, especially on sites with many authors.

Executive priority

Treat this as a moderate WordPress hygiene issue. Prioritize sites with public traffic, multiple contributors, or weak account controls. Patch and review content promptly, but the provided evidence does not support emergency active-exploitation handling.

Technical view

The reported flaw is insufficient sanitization and output escaping in Avada's update_layout function, mapped to CWE-79. It requires authenticated low-privilege access and has CVSS 3.1 score 6.4. Source version details conflict: the title says through 6.2.2, while the description says through 6.2.3.

Likely exposure

Exposure is most likely on WordPress sites using Avada with contributor, author, editor, or administrator accounts. Sites without untrusted authenticated content users have lower practical exposure, but compromised low-privilege accounts could still matter.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires authenticated contributor-level or higher access, then the stored script executes for users who access the affected page.

Researcher notes

The key uncertainty is version scope. The CVE bundle says Avada up to and including 6.2.3, while the title and vendor reference imply a 6.2.3 security fix. Validate against primary vendor guidance before declaring remediation complete.

Mitigation direction

  • Inventory WordPress sites using the Avada theme.
  • Check installed Avada versions against vendor and Wordfence guidance.
  • Update Avada to a vendor-supported fixed release.
  • Restrict contributor-level access to trusted users only.
  • Review recently modified layouts and pages for suspicious script content.
  • Monitor WordPress accounts for unexpected contributor or editor activity.

Validation and detection

  • Confirm whether Avada is installed and active on each WordPress site.
  • Record the exact Avada version from WordPress administration or asset inventory.
  • Verify contributor, author, editor, and administrator accounts are expected.
  • Review affected pages and layouts for unexpected embedded scripts.
  • Check web application logs for suspicious authenticated content changes.
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-79: 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-36711 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
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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
4Source 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
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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
ThemeFusionAvada | Website Builder For WordPress & WooCommerce0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.