dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-6325

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Incorrect Privilege Assignment vulnerability in KingAddons.com King Addons for Elementor king-addons allows Privilege Escalation.This issue affects King Addons for Elementor: from n/a through <= 51.1.36.

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

A privilege escalation vulnerability exists in King Addons for Elementor plugin where incorrect privilege assignment allows users to gain elevated access beyond their intended role. The vulnerability affects versions through 51.1.36 and has a critical CVSS score of 9.8, indicating ease of exploitation and complete compromise potential.

MitigationUpdate King Addons for Elementor to the latest patched version immediately upon availability. Audit all user accounts, especially those with administrative privileges, to detect any unauthorized privilege escalation that may have occurred.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify King Addons for Elementor is installed
    Check your WordPress plugins directory or admin panel for the King Addons for Elementor plugin
    Affected if The plugin is present in the WordPress installation
  2. Determine installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate King Addons for Elementor to read the version number, or check the plugin header in the main plugin file
    Affected if Version displayed is 51.1.36 or lower
  3. Compare against affected range
    Compare your installed version number to the affected range: any version through 51.1.36 is vulnerable
    Affected if Installed version is 51.1.36 or any earlier version (e.g., 51.0.0, 50.x.x, etc.)
  4. Review user roles for unauthorized changes
    In WordPress admin, go to Users and audit all accounts for unexpected role assignments, particularly users granted Administrator or elevated privileges who should not have them
    Affected if Any user account has been escalated to a higher privilege level than originally assigned

A user is affected if King Addons for Elementor version 51.1.36 or earlier is installed and active in their WordPress 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update King Addons for Elementor to the latest patched version immediately upon availability. Audit all user accounts, especially those with administrative privileges, to detect any unauthorized privilege escalation that may have occurred.

Recommended fix Moderate confidence

Any version released after 51.1.36 (verify the specific latest stable release on KingAddons.com)

  1. 1. Log in to the WordPress admin dashboard where King Addons for Elementor is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate King Addons for Elementor in the plugin list
  4. 4. Check the current installed version number to confirm it is <= 51.1.36
  5. 5. If vulnerable, click 'Update Now' if an update is available, or manually download the latest version from KingAddons.com or WordPress.org
  6. 6. After updating, verify the new version number reflects a version higher than 51.1.36
  7. 7. Test key functionality on the site to ensure the plugin update did not break existing Elementor-based pages
  8. 8. Clear any caching mechanisms (site cache, CDN cache) after the update
Caveat Review King Addons changelog for any breaking changes between your current version and the new version; test in staging if possible before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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