dbcve.org
Premium AddonsWordPress extension · Leap13

CVE-2023-37868

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 2.9.0 or later.
See remediation →
71/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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Leap13 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 · low confidence

Premium Addons PRO plugin for WordPress/Elementor contains an information disclosure vulnerability allowing unauthorized actors to access sensitive data. The flaw exists across all versions up to and including 2.9.0.

MitigationUpdate Premium Addons PRO to the latest version (beyond 2.9.0) to remediate the vulnerability. Ensure a backup is performed before updating and verify Elementor page builder functionality post-update.

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.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Locate Premium Addons PRO plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Premium Addons PRO' or use wp-cli: wp plugin list --name='premium-addons-pro' --format=table
    Affected if Plugin version is 2.9.0 or lower
  2. Confirm plugin is active
    Verify the Premium Addons PRO plugin status in Plugins list shows as 'Active', or check with wp-cli: wp plugin is-active premium-addons-pro
    Affected if Plugin is installed and active in the WordPress environment
  3. Check for unauthorized endpoint exposure
    The vulnerability allows unauthenticated access to sensitive data - test if the plugin REST API or ajax endpoints are accessible without authentication by reviewing network requests or consulting the plugin documentation for protected endpoints
    Affected if Plugin endpoints respond to unauthenticated requests exposing sensitive data

You are affected if Premium Addons PRO version 2.9.0 or lower is installed and active in your WordPress/Elementor environment.

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
Upgrade available Upgrade to a release after 2.9.0
Interim mitigation

Update Premium Addons PRO to the latest version (beyond 2.9.0) to remediate the vulnerability. Ensure a backup is performed before updating and verify Elementor page builder functionality post-update.

Fix this in Premium Addons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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