dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-35050

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Missing Authorization vulnerability in Elementor Elementor Pro.This issue affects Elementor Pro: from n/a through 3.13.0.

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 confidence

Missing Authorization vulnerability in Elementor Pro allows attackers to access certain functionality without proper authorization checks. The specific affected functions and attack vector are not detailed in the available description, but the vulnerability exists across versions up to 3.13.0.

MitigationUpdate Elementor Pro to the latest version beyond 3.13.0 to receive vendor patches addressing the missing authorization checks, or implement access control validation on affected endpoints if patching is not immediately feasible.

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 checks

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

  1. Confirm Elementor Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate Elementor Pro in the list
    Affected if Elementor Pro appears in the installed plugins list
  2. Find installed version number
    Click on the Elementor Pro plugin entry to expand its details; the version number is displayed in the plugin metadata
    Affected if Version number is visible and is 3.13.0 or earlier
  3. Compare version to affected range
    Compare your installed version against the affected range: versions up to and including 3.13.0
    Affected if Installed version is 3.13.0 or any version prior to 3.13.0
  4. Review access logs for unauthorized requests
    Examine WordPress audit logs or server access logs for unusual or unauthorized POST requests to Elementor Pro endpoints that may indicate exploitation of missing authorization
    Affected if Unauthorized access attempts to Elementor Pro functions are found in logs

If Elementor Pro is installed and the version is 3.13.0 or earlier, the environment is affected by the missing authorization vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Elementor Pro to the latest version beyond 3.13.0 to receive vendor patches addressing the missing authorization checks, or implement access control validation on affected endpoints if patching is not immediately feasible.

Recommended fix Moderate confidence

Elementor Pro 3.13.1 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Elementor Pro in the plugin list
  4. Check if the current version is 3.13.0 or earlier
  5. If vulnerable, click Update Now to update to the latest version, or manually download the latest version from elementor.com and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35050 — 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-2023-35050 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