DiviWordPress extension · Elegantthemes
CVE-2023-29099
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Elegant themes Divi theme <= 4.20.2 versions.
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 · moderate confidenceStored XSS vulnerability in Divi theme allows authenticated users with contributor+ privileges to inject malicious scripts through theme functionality. The vulnerability is persistent and affects all sites running Divi theme versions 4.20.2 and below.
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
<= 4.20.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Divi theme is installedNavigate to Appearance > Themes in WordPress admin panel and verify the Divi theme is active, or check the /wp-content/themes/ directory for the divi folderAffected if Divi theme is the active theme or installed on the WordPress site
-
Identify installed Divi versionCheck the style.css file in /wp-content/themes/Divi/ for the version header, or view the theme details in Appearance > Themes in WordPress adminAffected if The version listed is 4.20.2 or lower
-
Verify contributor-level user access existsNavigate to Users in WordPress admin and review user roles; contributor role or higher provides authenticated accessAffected if At least one user account has contributor, author, editor, or administrator privileges
-
Inspect theme content storage for malicious scriptsSearch WordPress database tables (wp_posts, wp_postmeta) for script tags or encoded JavaScript in content fields associated with Divi theme builder or module contentAffected if Unsanitized script tags are found stored in the database related to Divi content
If the Divi theme version is 4.20.2 or below and contributor+ user accounts exist on the site, the environment is affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Divi theme to a version newer than 4.20.2. If updates are not immediately possible, implement input sanitization and output encoding for user-supplied content in theme rendering paths.
Divi theme version 4.20.3 or later
- Upgrade the Divi theme to a version newer than 4.20.2 (e.g., 4.20.3 or latest stable release)
- After upgrading, verify the fix by testing the affected functionality where the stored XSS vulnerability existed
- Ensure all contributors and users are aware of the update
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
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 locallyCheck whether your project pulls in CVE-2023-29099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29099 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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