Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2020-35945

Divi

Elegant Themes / Divi

Watch CVE-2020-35945 Browse KEV feed
Severity
CVSS 9.9 · Critical
Confidence
High
Exploit status
Exploited in the wild
EPSS
2.5%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2020-35945 is a vulnerability affecting Elegant Themes Divi. An issue was discovered in the Divi Builder plugin, Divi theme, and Divi Extra theme before 4.5.3 for WordPress. Authenticated attackers, with...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Elegant Themes / Divi.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

An issue was discovered in the Divi Builder plugin, Divi theme, and Divi Extra theme before 4.5.3 for WordPress

An issue was discovered in the Divi Builder plugin, Divi theme, and Divi Extra theme before 4.5.3 for WordPress. Authenticated attackers, with contributor-level or above capabilities, can upload arbitrary files, including .php files.

This occurs because the check for file extensions is on the client side.

Published
01 Jan 2021
Exploitation Reported
04 Aug 2020
Attack vector
Remote
Complexity
Low
Privileges
Low
User interaction
None

Tags

php wordpress

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

Wordfence

Recorded 04 Aug 2020

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
Wordfence First 2020-08-04 05:57 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.9 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

2.5%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Unrestricted Upload of File with Dangerous Type CWE-434

All CVSS Scores

CVSS v3.1 9.9 Critical

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

CVSS v2.0 6.5 Medium

AV:N/AC:L/Au:S/C:P/I:P/A:P

Timeline

From disclosure to observed exploitation

  1. 03:28 UTC

    CVE published

    Vulnerability disclosed publicly

  2. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

  3. 05:57 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2020-35945

Sample API response 
{
  "cve_id": "CVE-2020-35945",
  "confidence": "High",
  "cvss_score": 9.9,
  "cvss_estimated": false,
  "epss_score": 0.02451,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}