# CVE-2025-13563: Lizza LMS Pro <= 1.0.3 - Unauthenticated Privilege Escalation

> Unauthenticated attackers can register as administrators due to missing role restrictions in the Lizza LMS Pro plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-vjww-2j24-c357

## What is CVE-2025-13563?

CVE-2025-13563 is a critical vulnerability in BuddhaThemes Lizza LMS Pro, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-13563?


## How do I fix CVE-2025-13563?

No fix has been published for CVE-2025-13563 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13563 being exploited?

There is no known exploitation of CVE-2025-13563 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13563 and fix it if it is affected.

What it is: CVE-2025-13563 is a critical vulnerability in BuddhaThemes Lizza LMS Pro, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13563 in the wild and no public exploit code.

Affected product: BuddhaThemes Lizza LMS Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13563/ (Markdown: https://insights.sbomify.com/CVE-2025-13563/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13563
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13563
- OSV: https://osv.dev/vulnerability/CVE-2025-13563

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13563/
Summaries are generated and may contain mistakes; the official description above is the record.