CVE-2025-15347
Privilege Escalation in Creator LMS via Missing Capability Check
Publication date: 2026-01-20
Last updated on: 2026-01-20
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| creatorlms | creator_lms | to 1.1.12 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Creator LMS WordPress plugin allows authenticated users with contributor-level access or higher to modify arbitrary WordPress options without proper authorization. This happens because the plugin's get_items_permissions_check function lacks a proper capability check, enabling privilege escalation by updating sensitive plugin settings via the REST API. [1]
How can this vulnerability impact me? :
An attacker with contributor-level access could exploit this vulnerability to escalate their privileges by modifying critical WordPress options related to the Creator LMS plugin. This could lead to unauthorized changes in plugin settings, potentially compromising site integrity, security, and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if your Creator LMS plugin version is 1.1.12 or below, as these versions lack proper permission checks allowing unauthorized updates. To detect exploitation attempts, monitor REST API requests to the CreatorLMS settings endpoint for unauthorized update attempts. For example, you can use commands like `grep` on your web server logs to find suspicious REST API calls: `grep '/wp-json/creatorlms/v1/settings' /path/to/access.log | grep -i 'POST\|PUT'` to identify update attempts. Additionally, check user roles with contributor level or above making such requests. However, no specific detection commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Creator LMS plugin to version 1.1.13 or later, where the vulnerability is fixed. This update includes stricter permission checks requiring the `manage_options` capability for updating settings and validates option keys to prevent unauthorized modifications. Until you can update, restrict contributor-level users from accessing REST API endpoints related to CreatorLMS settings or limit their permissions to prevent exploitation. [1]