dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-14802

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 LearnPress – WordPress LMS Plugin for WordPress is vulnerable to unauthorized file deletion in versions up to, and including, 4.3.2.2 via the /wp-json/lp/v1/material/{file_id} REST API endpoint. This is due to a parameter mismatch between the DELETE operation and authorization check, where the endpoint uses file_id from the URL path but the permission callback validates item_id from the request body. This makes it possible for authenticated attackers, with teacher-level access, to delete arbitrary lesson material files uploaded by other teachers via sending a DELETE request with their own item_id (to pass authorization) while targeting another teacher's file_id.

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 LearnPress WordPress LMS plugin has an authorization bypass in its REST API material deletion endpoint. The DELETE operation targets file_id from the URL path, but the permission callback validates item_id from the request body, allowing authenticated teachers to bypass ownership checks and delete files belonging to other teachers.

MitigationApply vendor patch when available; alternatively, modify the permission callback to validate the authenticated user owns the file_id being targeted rather than relying on item_id from the request body.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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. Confirm LearnPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for LearnPress or LearnPress - WordPress LMS Plugin. Alternatively, check the file /wp-content/plugins/learnpress/ exists.
    Affected if LearnPress plugin is not installed or not active
  2. Determine installed LearnPress version
    In WordPress admin_plugins list, click on LearnPress to view details and note the version number. Or check the version in /wp-content/plugins/learnpress/readme.txt or in the plugin header of /wp-content/plugins/learnpress/learnpress.php.
    Affected if Version is within the affected range (compare to vendor advisories)
  3. Verify REST API is accessible
    Send a GET request to /wp-json/learnpress/v1/ or /wp-json/ endpoint and confirm it returns a valid response indicating the REST API is enabled.
    Affected if REST API is disabled or returns error (vulnerability requires REST API access)
  4. Check for teacher-level user accounts
    In WordPress admin, go to Users and look for users with Teacher role (LearnPress creates this role). Alternatively, query wp_usermeta for meta_key='learnpress_teacher' and meta_value=1.
    Affected if No teacher accounts exist (vulnerability requires authenticated teacher access)
  5. Inspect the permission callback logic
    Examine the REST API endpoint definition in /wp-content/plugins/learnpress/includes/rest-api/class-lp-rest-material.php or similar file. Look for the delete_files endpoint and verify if the permission callback validates file_id from URL path rather than item_id from request body.
    Affected if The permission callback validates item_id from request body instead of file_id from URL path (vulnerable code pattern)

User is affected if LearnPress is installed with a vulnerable version, REST API is enabled, teacher-level users exist, and the permission callback incorrectly validates item_id from request body instead of file_id from the URL path.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; alternatively, modify the permission callback to validate the authenticated user owns the file_id being targeted rather than relying on item_id from the request body.

Recommended fix Moderate confidence

LearnPress version 4.3.3 or later

  1. 1. Log in to the WordPress admin dashboard with administrator credentials
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the LearnPress plugin in the list
  4. 4. Check the current installed version of LearnPress
  5. 5. If the installed version is 4.3.2.2 or earlier, click the 'Update now' link if an update is available, or manually download the latest version from the WordPress plugin repository
  6. 6. Before updating, consider creating a full site backup including database
  7. 7. Test the update in a staging environment if possible, particularly the lesson material upload and deletion functionality
  8. 8. After updating, verify that teacher-level users can only delete their own uploaded materials and not those of other teachers
Caveat No significant breaking changes expected; this is a security patch addressing an authorization bypass

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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