dbcve.org
Premium AddonsWordPress extension · Leap13

CVE-2024-1996

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 plugin's IHover widget link in all versions up to, and including, 2.9.12 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions 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

Premium Addons PRO WordPress plugin versions up to 2.9.12 contain a stored XSS vulnerability in the IHover widget link functionality. Authenticated attackers with contributor-level or higher permissions can inject arbitrary JavaScript through unsanitized user-supplied attributes, which then executes when other users access the affected pages due to insufficient output escaping.

MitigationUpdate Premium Addons PRO to version 2.9.13 or later. Audit existing pages using the IHover widget for injected malicious scripts and remove any identified payloads.

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Premium Addons PRO' in the list
    Affected if Plugin is present in the WordPress installation
  2. Check installed plugin version
    Click on the plugin in the Plugins list to view its details, or check the plugin's main PHP file for a version constant
    Affected if Version is lower than 2.9.13 (the version number appears below the plugin name in the plugins list)
  3. Identify pages using the IHover widget
    In Elementor editor, search for 'IHover' widget in the widget panel. Alternatively, search the WordPress database in wp_posts for content containing 'ihover' or review Elementor saved templates
    Affected if Any pages, posts, or templates contain the IHover widget
  4. Inspect IHover widget link settings
    Edit any page containing the IHover widget, click on the widget, and expand the Link or Hover Effects section. Look for any URL/link fields that accept user input
    Affected if The widget has link fields that accept custom URLs and these are not being properly escaped when rendered on the frontend

You are affected if Premium Addons PRO version is below 2.9.13 AND you have pages using the IHover widget with custom link settings that could accept unsanitized input.

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. Audit existing pages using the IHover widget for injected malicious scripts and remove any identified payloads.

Recommended fix High confidence

2.9.13

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Premium Addons PRO' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.9.13 or higher
  5. Verify the updated version number reflects 2.9.13 or later
  6. Clear any site caching if applicable

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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