CVE-2026-1829
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 · uneditedThe Content Visibility for Divi Builder plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.02 via the 'et_pb_text' shortcode 'cvdb_content_visibility_check' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.
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 confidenceThe Content Visibility for Divi Builder WordPress plugin allows authenticated users with Contributor-level access or higher to execute arbitrary code on the server via the 'cvdb_content_visibility_check' parameter in the 'et_pb_text' shortcode. This parameter is not properly sanitized, enabling RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Content Visibility for Divi Builder'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.Affected if The installed version is 4.02 or any version lower than 4.02.
-
Confirm et_pb_text shortcode is availableSearch your WordPress database or theme files for occurrences of the 'et_pb_text' shortcode, or check pages/posts in the Divi Builder that use the Text module.Affected if The et_pb_text shortcode is present and actively used on the site.
-
Inspect for vulnerable cvdb_content_visibility_check parameterReview posts, pages, or custom post types that use the et_pb_text shortcode. Look for the 'cvdb_content_visibility_check' parameter in the shortcode attributes.Affected if Any published content contains the cvdb_content_visibility_check parameter in an et_pb_text shortcode.
-
Verify user role permissionsGo to WordPress admin > Users and review which roles have access to create or edit content. Check if any roles below Administrator (such as Contributor or Author) can publish or edit posts containing shortcodes.Affected if Users with Contributor-level access or higher can create or edit content on the site.
You are affected if the plugin version is 4.02 or lower AND the et_pb_text shortcode with the cvdb_content_visibility_check parameter is in use on your site AND untrusted users have Contributor-level access or higher.
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.
From vendor dataUpdate the plugin to a version beyond 4.02 immediately. If no patched version is available, disable or remove the plugin. Additionally, review user accounts and audit logs for signs of exploitation.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1829 — 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-2026-1829 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