dbcve.org
Premium AddonsWordPress extension · Leap13

CVE-2023-37869

HIGH · 8.8 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 2.9.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Premium Addons Premium Addons PRO.This issue affects Premium Addons PRO: from n/a through 2.9.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

Premium Addons PRO, a popular Elementor page builder addon plugin for WordPress, contains a missing authorization vulnerability that allows authenticated users to access functionality or data they should not have permission to access. The vulnerability exists across versions up to 2.9.0, potentially allowing privilege escalation or unauthorized modification of site content.

MitigationUpdate to the latest version of Premium Addons PRO once a patch is released. In the interim, restrict user permissions to the lowest necessary role and monitor for suspicious administrative actions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Premium AddonsWordPress extension
Affected:< 2.9.1

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 checks

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

  1. Confirm Premium Addons PRO is installed
    Access WordPress admin panel, go to Plugins > Installed Plugins, and search for 'Premium Addons PRO' or 'Leap13 Premium Addons'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'premium-addons-pro' or similar Leap13 plugin folders.
    Affected if The plugin from Leap13 (Premium Addons PRO) appears in the installed plugins list.
  2. Identify the installed version
    In WordPress admin, click on the plugin to view its details and locate the version number displayed under the plugin name. Alternatively, check the main plugin PHP file (usually in the plugin folder) for a 'Version:' comment in the file header, or examine the readme.txt file for the version entry.
    Affected if The version number is lower than 2.9.1 (for example, 2.9.0, 2.8.x, or earlier).
  3. Verify the plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm that Premium Addons PRO shows as 'Active' under the plugin status column.
    Affected if The plugin is currently active on the WordPress site.
  4. Review user roles with elevated permissions
    In WordPress admin, go to Users > All Users and review the list of existing user accounts. Check if any users have been added or modified recently, particularly accounts with Administrator, Editor, or Author roles that you did not create.
    Affected if Unexpected user accounts exist, or existing accounts have been granted higher privileges than intended.

A user is affected if Premium Addons PRO from Leap13 is installed, active, and running a version lower than 2.9.1, allowing authenticated users to potentially escalate privileges or modify content without proper authorization.

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
Upgrade available Upgrade to 2.9.1 or later
Fixed in 2.9.1
Interim mitigation

Update to the latest version of Premium Addons PRO once a patch is released. In the interim, restrict user permissions to the lowest necessary role and monitor for suspicious administrative actions.

Recommended fix Moderate confidence

Premium Addons PRO 2.9.1

  1. Backup the WordPress site before making any changes
  2. Update Premium Addons PRO to version 2.9.1 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly via the WordPress repository if available)
  3. Verify the update was successful by checking the plugin version
  4. Test the site functionality to ensure the update did not break existing features

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

Fix this in Premium Addons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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