dbcve.org
DiviWordPress extension · Elegantthemes

CVE-2024-5533

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-18
Fix available
A fix is available. Upgrade to 4.25.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.25.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Divi WordPress theme versions up to 4.25.1 contain a stored Cross-Site Scripting (XSS) vulnerability due to inadequate input sanitization and output escaping. Authenticated users with Author-level permissions or higher can inject malicious JavaScript payloads into pages, which then executes when other users view those compromised pages.

MitigationUpdate the Divi theme to a version newer than 4.25.1. If immediate updating is not feasible, implement proper input sanitization and output escaping on all user-controllable inputs within the theme, and consider restricting user permissions until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DiviWordPress extension
Affected:< 4.25.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Divi theme is installed
    Access your WordPress admin dashboard and navigate to Appearance > Themes to confirm the Divi theme is active on the site.
    Affected if Divi theme is listed as the active theme
  2. Determine installed Divi version
    Check the Divi theme version by reviewing the style.css file within the Divi theme folder, typically found at /wp-content/themes/Divi/style.css, or view the theme details in Appearance > Themes.
    Affected if Unable to retrieve a version number or version shows as unknown
  3. Compare version against affected range
    Review the version number identified in step 2 and compare it against the affected range: versions prior to 4.25.2 are vulnerable.
    Affected if Installed version is lower than 4.25.2 (e.g., 4.25.1, 4.25.0, earlier versions)
  4. Identify users with Author-level or higher access
    Navigate to Users > All Users in the WordPress admin panel and review user roles. Author, Editor, and Administrator roles all have permissions that could allow exploiting this vulnerability.
    Affected if One or more users with Author, Editor, or Administrator roles exist on the site

A site is affected if the Divi theme version is installed and is lower than 4.25.2, combined with the presence of users possessing Author-level permissions or higher who could inject malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.25.2 or later
Fixed in 4.25.2
Interim mitigation

Update the Divi theme to a version newer than 4.25.1. If immediate updating is not feasible, implement proper input sanitization and output escaping on all user-controllable inputs within the theme, and consider restricting user permissions until the patch can be applied.

Recommended fix High confidence

Divi theme version 4.25.2

  1. Create a complete backup of your WordPress site (database and files) before proceeding with any updates
  2. Navigate to your WordPress dashboard and go to Appearance > Themes
  3. Locate the Divi theme and check if version 4.25.2 is available for update
  4. Update Divi to version 4.25.2
  5. After updating, verify the theme version shows 4.25.2 in the Themes section
  6. Test that the Divi Builder and related functionality work correctly on your pages

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Divi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5533 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data