dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-56225

HIGH · 8.8 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 4.10.57 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 Leap13 Premium Addons for Elementor premium-addons-for-elementor allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Premium Addons for Elementor: from n/a through <= 4.10.56.

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

Missing authorization vulnerability in Leap13 Premium Addons for Elementor plugin allows users to access functionality that should be constrained by access control lists. The plugin fails to properly validate user capabilities before executing certain sensitive functions, potentially allowing unauthenticated or lower-privileged users to perform actions reserved for administrators.

MitigationUpdate Premium Addons for Elementor to version 4.10.57 or later. Review user role and capability configurations in WordPress admin and ensure least-privilege principles are 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 Addons For ElementorWordPress extension
Affected:< 4.10.57

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. Locate the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Premium Addons for Elementor and read the version number displayed under the plugin name, or check the version listed in the plugin's main PHP file header.
    Affected if The displayed version number is lower than 4.10.57
  2. Verify the plugin is active
    Confirm the Premium Addons for Elementor plugin shows as 'Active' in the WordPress Plugins admin page.
    Affected if The plugin is active and the version is below 4.10.57
  3. Review server access logs for plugin-related endpoints
    Examine web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to wp-admin/admin-ajax.php or other plugin-specific AJAX handlers originating from unauthenticated or low-privilege IP addresses.
    Affected if Requests to plugin AJAX endpoints are observed from users without administrator privileges
  4. Check for unauthorized configuration changes
    Review WordPress postmeta, options, or custom tables that store Premium Addons settings for any unexpected modifications that could indicate unauthorized administrative access.
    Affected if Plugin settings have been modified without admin-level authentication

A user is affected if Premium Addons for Elementor is active at a version below 4.10.57, regardless of whether exploitation is yet observed.

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 4.10.57 or later
Fixed in 4.10.57
Interim mitigation

Update Premium Addons for Elementor to version 4.10.57 or later. Review user role and capability configurations in WordPress admin and ensure least-privilege principles are applied.

Recommended fix High confidence

4.10.57

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Premium Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 4.10.57 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version shows 4.10.57 to confirm the patch is applied

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

Fix this in Premium Addons For Elementor 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-56225 — 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-56225 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