Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13563: CWE-269 Improper Privilege Management in BuddhaThemes Lizza LMS Pro

0
Critical
VulnerabilityCVE-2025-13563cvecve-2025-13563cwe-269
Published: Thu Feb 19 2026 (02/19/2026, 04:36:20 UTC)
Source: CVE Database V5
Vendor/Project: BuddhaThemes
Product: Lizza LMS Pro

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.

AI-Powered Analysis

AILast updated: 02/19/2026, 05:25:54 UTC

Technical Analysis

CVE-2025-13563 is a critical security vulnerability identified in the BuddhaThemes Lizza LMS Pro plugin for WordPress, affecting all versions up to and including 1.0.3. The root cause is improper privilege management (CWE-269) in the 'lizza_lms_pro_register_user_front_end' function, which fails to restrict the user roles that can be assigned during front-end user registration. This flaw allows unauthenticated attackers to specify the 'administrator' role when registering a new user account, thereby gaining full administrative privileges on the WordPress site. The vulnerability does not require any prior authentication or user interaction, making it trivially exploitable remotely over the network. The CVSS v3.1 base score of 9.8 reflects the critical nature of this vulnerability, with attack vector being network (AV:N), no attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and full impact on confidentiality, integrity, and availability (C:H/I:H/A:H). This means an attacker can completely compromise the affected system, potentially leading to data theft, site defacement, malware deployment, or pivoting to internal networks. Although no public exploits have been reported yet, the simplicity of exploitation and the widespread use of WordPress and LMS plugins make this a high-risk issue. The lack of available patches at the time of disclosure increases the urgency for mitigation. Organizations using Lizza LMS Pro should consider immediate protective measures such as disabling user self-registration or implementing custom role validation until an official patch is released.

Potential Impact

For European organizations, this vulnerability poses a severe risk to the confidentiality, integrity, and availability of their WordPress-based learning management systems. Successful exploitation grants attackers full administrative control, enabling them to manipulate content, steal sensitive data, deploy ransomware or other malware, and disrupt services. Educational institutions, corporate training platforms, and e-learning providers relying on Lizza LMS Pro are particularly vulnerable. The compromise of administrator accounts can also serve as a foothold for lateral movement within organizational networks, potentially exposing broader IT infrastructure. Given the critical nature of the vulnerability and the ease of exploitation, the impact could include significant operational disruption, reputational damage, regulatory penalties under GDPR for data breaches, and financial losses. The threat is heightened in sectors with stringent data protection requirements and high reliance on digital learning platforms.

Mitigation Recommendations

Immediate mitigation steps include disabling the front-end user registration feature in Lizza LMS Pro to prevent unauthorized account creation. Administrators should audit existing user accounts for unauthorized administrator roles and remove any suspicious accounts. Implementing web application firewall (WAF) rules to block requests attempting to assign the administrator role during registration can provide temporary protection. Organizations should monitor logs for unusual registration activity and failed or successful privilege escalations. Until an official patch is released, consider deploying custom code or plugins that enforce strict role assignment policies during user registration. Regular backups of the WordPress site and database should be maintained to enable recovery in case of compromise. Once a vendor patch becomes available, it should be applied promptly. Additionally, organizations should review their WordPress security posture, including limiting plugin usage to trusted sources and enforcing the principle of least privilege for all user accounts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-22T17:13:16.491Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699697f26aea4a407a3bdfcc

Added to database: 2/19/2026, 4:56:18 AM

Last enriched: 2/19/2026, 5:25:54 AM

Last updated: 2/20/2026, 9:50:51 PM

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats