dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62889

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 KingAddons.com King Addons for Elementor king-addons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects King Addons for Elementor: from n/a through <= 51.1.61.

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

This is a missing authorization vulnerability (also classified as Insecure Direct Object Reference or broken access control) in the King Addons for Elementor WordPress plugin. The vulnerability allows authenticated or unauthenticated attackers to access functionality or data that should require proper authorization, due to incorrectly configured access control security levels in the plugin through version 51.1.61.

MitigationUpdate King Addons for Elementor to the latest version once available. If no patch exists, review the plugin's access control configurations and implement proper authorization checks on all user-facing endpoints and sensitive functions.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 King Addons for Elementor is installed
    Check your WordPress plugins directory (wp-content/plugins) for the 'king-addons' folder, or query the wp_options table for 'active_plugins' to see if the plugin is enabled.
    Affected if The plugin folder exists and the plugin is active in WordPress.
  2. Identify the installed plugin version
    Open the main plugin file (king-addons-for-elementor.php) and look for the 'Version' header in the plugin comment block, or query the wp_options table for the option_name containing 'king_addons' version information.
    Affected if The version number displayed is 51.1.61 or lower.
  3. Confirm vulnerability applies to your version
    Compare your installed version against the affected range. If your version is 51.1.61 or below, the missing authorization vulnerability is present in your environment.
    Affected if Installed version is less than or equal to 51.1.61.
  4. Review access to sensitive plugin endpoints
    Use a browser or HTTP tool to access common King Addons admin AJAX endpoints (like wp-admin/admin-ajax.php?action=king_addons_) while logged out. Check if the plugin returns sensitive data or performs actions without requiring authentication.
    Affected if AJAX or other endpoints respond with data or perform actions without requiring valid WordPress authentication.
  5. Check for publicly accessible plugin modules
    Inspect your site's public-facing pages for King Addons widgets. If any widgets load data or configurations that should be restricted (like post/option queries), test accessing them as an unauthenticated user.
    Affected if Unauthenticated users can view or trigger plugin functionality that should require elevated privileges.

You are affected if King Addons for Elementor is installed with version 51.1.61 or lower and unauthorized users can access plugin functions or data that should require proper authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update King Addons for Elementor to the latest version once available. If no patch exists, review the plugin's access control configurations and implement proper authorization checks on all user-facing endpoints and sensitive functions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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