dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-13563

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
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
The Lizza LMS Pro plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.3. This is due to the 'lizza_lms_pro_register_user_front_end' function not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site.

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 Lizza LMS Pro WordPress plugin (versions up to 1.0.3) contains a privilege escalation vulnerability in its front-end user registration function 'lizza_lms_pro_register_user_front_end'. The function fails to validate or restrict the user role parameter, allowing unauthenticated attackers to register with the 'administrator' role and gain full admin access to the WordPress site.

MitigationUpdate to a patched version of the plugin immediately. If no patched version is available, disable the plugin's user registration functionality and audit existing user accounts for unauthorized administrator accounts created through this vulnerability.

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. Identify the installed version of Lizza LMS Pro
    Access your WordPress admin dashboard, navigate to Plugins, locate Lizza LMS Pro, and note the installed version number. Alternatively, inspect the main plugin file (typically named lizza-lms-pro.php or similar in wp-content/plugins/) and read the Version header comment.
    Affected if The installed version is lower than 1.0.4, indicating the vulnerable code is present.
  2. Confirm front-end registration functionality is exposed
    Visit the site front-end and locate any user registration page, form, or endpoint provided by the Lizza LMS Pro plugin. Check if the registration form accepts a role parameter (visible in HTML source or form fields).
    Affected if A public-facing registration form exists and accepts role input, allowing the vulnerable function lizza_lms_pro_register_user_front_end to be reached by unauthenticated users.
  3. Inspect WordPress user roles for unauthorized administrators
    In the WordPress admin dashboard, go to Users > All Users and review the list of users with the Administrator role. Look for any accounts that should not have administrator privileges or were created unexpectedly.
    Affected if Any administrator-level account exists that was not created by legitimate site administrators, indicating successful exploitation.
  4. Review server access logs for registration POST requests
    Examine web server access logs (Apache, Nginx, or hosting provider logs) for POST requests to registration endpoints containing a role parameter set to 'administrator' or similar elevated privileges.
    Affected if Logs show unauthenticated registration requests with a role parameter, confirming exploitation attempts or successful privilege escalation.

You are affected if the Lizza LMS Pro plugin version is below 1.0.4 AND the plugin's front-end registration is publicly accessible, as this allows unauthenticated attackers to register as administrators.

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 to a patched version of the plugin immediately. If no patched version is available, disable the plugin's user registration functionality and audit existing user accounts for unauthorized administrator accounts created through this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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