dbcve.org
Premium AddonsWordPress extension · Leap13

CVE-2024-2239

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 Premium Magic Scroll module 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 WordPress plugin (versions up to 2.9.12) contains a stored XSS vulnerability in the Premium Magic Scroll module. Authenticated users with contributor-level access can inject malicious JavaScript through unsanitized input fields, which is then stored and executed when other users access affected pages due to insufficient output escaping.

MitigationUpdate Premium Addons PRO to version 2.9.13 or later, which contains the security fix. Until then, review user permissions and restrict contributor-level access to untrusted users.

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. Check installed Premium Addons PRO version
    Navigate to WordPress dashboard > Plugins > Installed Plugins, locate Premium Addons PRO, and note the version number displayed
    Affected if Version is below 2.9.13 (versions 2.9.12 and earlier are affected)
  2. Identify if Premium Magic Scroll module is active
    Go to Premium Addons PRO settings or Elementor editor, look for the Magic Scroll widget/module, and verify whether it has been added to any pages or posts
    Affected if Magic Scroll is in use on any page or post in the site
  3. Inspect Magic Scroll widget settings for unsanitized content
    Edit pages containing the Magic Scroll widget, open the widget settings panel, and examine text input fields (such as scroll content, titles, or custom text fields) for unexpected HTML, script tags, or JavaScript event handlers
    Affected if Any Magic Scroll configuration contains raw HTML tags, script elements, or JavaScript code in input fields
  4. Review contributor-level user accounts
    Go to WordPress dashboard > Users, filter by the Contributor role, and audit which accounts exist and their activity
    Affected if There are contributor-level users who have access to create or edit content with the Magic Scroll module

The environment is affected if Premium Addons PRO version is below 2.9.13 AND the Magic Scroll module is being used on the site, allowing contributor-level users to inject malicious scripts.

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 contains the security fix. Until then, review user permissions and restrict contributor-level access to untrusted users.

Recommended fix High confidence

Premium Addons PRO version 2.9.13

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate Premium Addons PRO in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.9.13 or later from the WordPress repository
  5. After updating, verify the plugin version shows 2.9.13 or higher in the plugins list
  6. Clear any caching plugins or server-side caches to ensure the fixed version is served

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

Fix this in Premium Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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