CVE-2023-35046
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 · uneditedMissing Authorization vulnerability in Dynamic.ooo Dynamic Visibility for Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Dynamic Visibility for Elementor: from n/a through 5.0.5.
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 confidenceMissing authorization vulnerability in Dynamic.ooo Dynamic Visibility for Elementor plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to visibility control features, potentially enabling unauthorized modification of element visibility settings.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
-
Verify Dynamic Visibility for Elementor is installedCheck your WordPress plugin directory or admin panel to confirm the Dynamic.ooo Dynamic Visibility for Elementor plugin is present and activeAffected if Plugin is installed and active in WordPress
-
Confirm Elementor Page Builder is activeVerify that Elementor page builder plugin is also installed and active, as this vulnerability affects the integration between the two pluginsAffected if Both Dynamic Visibility and Elementor are active simultaneously
-
Inspect visibility control feature accessAttempt to access or modify element visibility settings through the plugin interface with a low-privilege user account (non-administrator) to test if authorization is properly enforcedAffected if Non-administrator users can access or modify visibility settings without proper permission validation
Environment is affected if Dynamic Visibility for Elementor plugin versions prior to 5.0.6 are installed and active alongside Elementor, with visibility control features accessible without proper authorization checks.
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 · scopedUpgrade Dynamic Visibility for Elementor to version 5.0.6 or later which includes proper authorization checks. Until patched, restrict backend access to trusted administrators only.
Version 5.0.6 or later (latest stable release)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Dynamic Visibility for Elementor' in the plugin list
- 4. Check the current installed version (should be 5.0.5 or lower if affected)
- 5. Navigate to Plugins > Add New > Upload Plugin, or check for an update notification
- 6. If an update is available, click 'Update Now' to install the latest version
- 7. Alternatively, download the latest version from wordpress.org or the official vendor site and upload/install it
- 8. After update, verify the plugin is running version 5.0.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35046 — 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-35046 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