dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15347

HIGH · 8.8 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Creator LMS – The LMS for Creators, Coaches, and Trainers plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check in the get_items_permissions_check function in all versions up to, and including, 1.1.12. This makes it possible for authenticated attackers, with contributor level access and above, to update arbitrary WordPress options.

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 Creator LMS WordPress plugin has a missing capability check in its get_items_permissions_check function, allowing authenticated users with contributor-level access to modify arbitrary WordPress options. This enables privilege escalation by allowing lower-privileged users to change settings like user roles or administrative configuration.

MitigationUpdate the Creator LMS plugin to version 1.1.13 or later which includes proper capability checks in the get_items_permissions_check function.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Creator LMS plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'creator-lms' or look for the plugin in WP Admin > Plugins. Locate the main plugin file (usually creator-lms.php) and read the version header comment.
    Affected if The Creator LMS plugin folder exists in the WordPress installation and contains the plugin files.
  2. Determine the installed plugin version
    Open the main plugin file (creator-lms.php) and locate the 'Version:' field in the file header comment. Alternatively, query the WordPress database: SELECT option_value FROM wp_options WHERE option_name LIKE '%plugin_version%' AND option_value LIKE '%creator-lms%';
    Affected if The version number found is lower than 1.1.13.
  3. Identify REST API endpoints exposed by the plugin
    Check the plugin source code for REST API registration calls (register_rest_route). Look in the includes/ or classes/ directories for files registering routes under 'creator-lms/v1/'. Also test: curl -s -X GET https://yourdomain.com/wp-json/creator-lms/v1/ -H 'Authorization: Bearer [contributor-user-token]'
    Affected if The plugin exposes REST API endpoints under the /wp-json/creator-lms/v1/ route that handle options or settings.
  4. Inspect the get_items_permissions_check function
    Search the plugin source code for the function 'get_items_permissions_check'. Examine its implementation to see if it calls current_user_can() or a similar capability check. The file is typically in includes/class-rest-api.php or similar.
    Affected if The get_items_permissions_check function exists but does NOT contain a proper capability check (e.g., current_user_can('manage_options') or equivalent), allowing contributor-level access.
  5. Test contributor-level access to privileged operations
    Authenticate as a user with the Contributor role. Make a REST API request to the plugin endpoints (e.g., POST to /wp-json/creator-lms/v1/options) attempting to modify WordPress options like user_roles or siteurl. Inspect the HTTP response code and whether the change is applied.
    Affected if A contributor-level user receives a successful (200 OK) response and can modify WordPress options or settings that should require Administrator privileges.

You are affected if the Creator LMS plugin is installed with a version before 1.1.13 AND the get_items_permissions_check function lacks proper capability validation, allowing contributor users to modify privileged WordPress options.

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 the Creator LMS plugin to version 1.1.13 or later which includes proper capability checks in the get_items_permissions_check function.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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