dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-5483

HIGH · 8.1 CVSS v3.1 Published 2025-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
The LC Wizard plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check in the ghl-wizard/inc/wp_user.php file in versions 1.2.10 to 1.3.0. This makes it possible for unauthenticated attackers to create new user accounts with the administrator role when the PRO functionality is enabled.

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 LC Wizard WordPress plugin lacks proper capability verification in the user creation function within ghl-wizard/inc/wp_user.php, allowing unauthenticated attackers to craft requests that create new administrator-level user accounts when the PRO feature is enabled.

MitigationUpdate the plugin to the latest version immediately to obtain the patched code, and audit existing WordPress user accounts for any unauthorized administrator accounts created by attackers.

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

CVSS:3.1/AV:N/AC:H/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. Identify LC Wizard plugin version
    In WordPress admin, go to Plugins > Installed Plugins > locate LC Wizard and read the version number displayed below the plugin name
    Affected if version is 1.2.10, 1.2.11, 1.2.12, 1.2.13, 1.3.0, or any version between 1.2.10 and 1.3.0 inclusive
  2. Check if PRO functionality is enabled
    Look for LC Wizard PRO settings in WordPress admin panel under LC Wizard menu, or inspect plugin files for PRO license/feature flags in configuration
    Affected if PRO functionality is active or a PRO license is currently validated
  3. Verify vulnerable file exists
    Check for the file at wp-content/plugins/lc-wizard/ghl-wizard/inc/wp_user.php or similar path under the plugins directory
    Affected if the file ghl-wizard/inc/wp_user.php exists in the plugin directory

Affected if LC Wizard plugin version is between 1.2.10 and 1.3.0 AND PRO functionality is enabled, allowing unauthenticated admin account creation through the missing capability check.

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 the plugin to the latest version immediately to obtain the patched code, and audit existing WordPress user accounts for any unauthorized administrator accounts created by attackers.

Recommended fix Moderate confidence

Latest version after 1.3.0 (check WordPress plugin repository for version 1.3.1 or higher)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the LC Wizard plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. If no update is available, consider temporarily disabling the PRO functionality until a patched version is released
  6. 6. Review existing user accounts for any unauthorized administrator accounts created by attackers
  7. 7. Remove any suspicious administrator accounts that were not created by legitimate administrators

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-5483 — 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-5483 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