Is CVE-2026-1829 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-1829 being exploited in the wild.

How severe is CVE-2026-1829?

High severity, with a CVSS score of 8.8, published 2 June 2026.

Which products and versions are affected?

WordPress Plugin Content Visibility for Divi Builder Content Visibility for Divi Builder up to, and including, 4.02.

Is there a fix for CVE-2026-1829?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-1829 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-1829?

Check whether you run WordPress Plugin Content Visibility for Divi Builder Content Visibility for Divi Builder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-1829: WordPress Content Visibility for Divi Builder RCE in et_pb_text shortcode

CVE-2026-1829 · Severity: high · CVSS 8.8 · Published 2026-06-02

The Content Visibility for Divi Builder plugin for WordPress, which allows site owners to control who sees specific page content, contains a critical security flaw. An attacker with basic contributor-level access can exploit this vulnerability to run unauthorized commands on the website's server. This could lead to a complete takeover of the site, theft of sensitive data, or the installation of malicious software.

Quick answers

Is CVE-2026-1829 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-1829 being exploited in the wild.
How severe is CVE-2026-1829?: High severity, with a CVSS score of 8.8, published 2 June 2026.
Which products and versions are affected?: WordPress Plugin Content Visibility for Divi Builder Content Visibility for Divi Builder up to, and including, 4.02.
Is there a fix for CVE-2026-1829?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-1829 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-1829?: Check whether you run WordPress Plugin Content Visibility for Divi Builder Content Visibility for Divi Builder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Content Visibility for Divi Builder plugin for WordPress is vulnerable to Remote Code Execution (RCE) due to improper control of code generation (CWE-94). The flaw exists within the 'cvdb_content_visibility_check' parameter of the 'et_pb_text' shortcode. An authenticated attacker with at least Contributor-level privileges can inject and execute arbitrary PHP code on the underlying server. This vulnerability affects all versions of the plugin up to and including 4.02. A patch appears to be available in subsequent updates (changeset 3543621).

Affected products

WordPress Plugin Content Visibility for Divi Builder up to, and including, 4.02

Timeline

2026-06-02: disclosed
2026-06-02: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.