dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-38480

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Certain Dev Booster Elementor Addons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booster Elementor Addons: from n/a through 1.4.9.

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

A missing authorization vulnerability in Booster Elementor Addons (versions through 1.4.9) allows unauthenticated or unauthorized users to access functionality they should not have access to due to incorrectly configured access control security levels. This is a broken access control issue where the plugin fails to properly verify user permissions before allowing access to certain features or data.

MitigationUpdate Booster Elementor Addons to the latest version once available, and audit access control configurations to ensure all sensitive endpoints properly enforce authorization checks.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Confirm Booster Elementor Addons is installed
    Navigate to WordPress admin > Plugins and locate 'Booster Elementor Addons' or check the plugins directory for the booster-elementor-addons folder
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin > Plugins > Installed Plugins, find Booster Elementor Addons and read the version number displayed under the plugin name
    Affected if The version is 1.4.9 or any earlier version (versions through 1.4.9 are affected)
  3. Verify if the plugin exposes sensitive endpoints
    Test access to common Booster Elementor endpoints (such as /wp-json/booster/v1/ endpoints) using a browser or curl tool while logged out or as a low-privilege user
    Affected if Requests to plugin endpoints return data or actions succeed without requiring proper authentication or authorization
  4. Check access control configuration
    Review the plugin settings in WordPress admin under Booster Elementor Addons settings, specifically looking for any access control, permission, or user role settings that may be misconfigured
    Affected if Access control settings allow unauthenticated users or lower-privileged roles to access admin-level functionality

A user is affected if Booster Elementor Addons version 1.4.9 or earlier is installed and unauthenticated or unauthorized users can access plugin features without proper permission checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Booster Elementor Addons to the latest version once available, and audit access control configurations to ensure all sensitive endpoints properly enforce authorization checks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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