dbcve.org
Premium AddonsWordPress extension · Leap13

CVE-2024-2000

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 2.9.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Premium Addons PRO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'navigation_dots' parameter of the Multi Scroll Widget in all versions up to, and including, 2.9.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Premium Addons PRO plugin for WordPress fails to properly sanitize the 'navigation_dots' parameter in its Multi Scroll Widget and does not escape output, allowing authenticated attackers with contributor-level access or higher to inject persistent malicious JavaScript that executes when users access affected pages.

MitigationUpdate Premium Addons PRO to version 2.9.13 or later which implements proper input sanitization and output escaping for the navigation_dots parameter. Alternatively, restrict contributor-level user permissions until the patch is applied.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Verify Premium Addons PRO is installed
    Log into WordPress Admin and navigate to Plugins > Installed Plugins. Locate 'Premium Addons PRO' or 'Leap13 Premium Addons' in the list of active plugins.
    Affected if The plugin is installed and active
  2. Check the installed version
    In the Plugins list, view the plugin details or check the plugin header in /wp-content/plugins/premium-addons-pro/ (or similar path) to read the Version field. Compare your version to the affected range: any version below 2.9.13 is vulnerable.
    Affected if Installed version is below 2.9.13
  3. Identify use of the Multi Scroll Widget
    Review published pages and posts for the Multi Scroll Widget. In WordPress Admin, check each page/post editor, or query the database for widget-related meta entries in wp_postmeta containing 'premium_multi_scroll' or 'navigation_dots' settings.
    Affected if The Multi Scroll Widget is present and configured on any published content
  4. Audit user roles with contributor-level access or higher
    Navigate to Users > All Users in WordPress Admin. Review the role column for any accounts assigned 'Contributor', 'Author', 'Editor', or 'Administrator' roles.
    Affected if At least one user account has contributor-level permissions or higher

If Premium Addons PRO is installed with a version below 2.9.13 and the Multi Scroll Widget is in use, the environment is vulnerable to stored XSS via the navigation_dots parameter.

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.13 or later
Fixed in 2.9.13
Interim mitigation

Update Premium Addons PRO to version 2.9.13 or later which implements proper input sanitization and output escaping for the navigation_dots parameter. Alternatively, restrict contributor-level user permissions until the patch is applied.

Recommended fix High confidence

Premium Addons PRO version 2.9.13

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Premium Addons PRO' in the plugin list
  4. Click 'Update Now' if an update is available, or manually update to version 2.9.13
  5. Verify the update completed successfully

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

Fix this in Premium Addons Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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