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

CVE-2026-11988

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 Create and Sell Online Courses plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.9.1 via the 'userId' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to view the course enrollment progress and completion data belonging to any instructor or administrator account on the site. This IDOR does not apply when the target user is a regular subscriber, as the guard correctly blocks cross-subscriber access; exploitation is limited to cases where the victim user holds the LP_TEACHER_ROLE or administrator role.

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 fails to validate authorization on the userId parameter in course enrollment data endpoints, allowing any authenticated subscriber to access sensitive course completion and progress data for instructors and administrators by manipulating the userId value. This IDOR vulnerability stems from missing access control checks on a user-controlled key.

MitigationUpdate LearnPress to version 4.3.9.2 or later which includes proper authorization validation on the userId parameter, or implement role-based access control checks before returning enrollment data.

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

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

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
    Check the WordPress plugins directory or access wp-admin > Plugins to see if LearnPress is active
    Affected if LearnPress plugin is installed and active on the WordPress site
  2. Identify the installed LearnPress version
    Navigate to Plugins > Installed Plugins > LearnPress, or inspect the main plugin file header for the Version field, or check the changelog file if accessible
    Affected if Installed version is lower than 4.3.9.2 (the fixed release)
  3. Verify WordPress user roles exist
    Go to Users > All Users in wp-admin to list registered accounts and their roles
    Affected if Any user account with 'Subscriber' role exists on the site
  4. Confirm enrollment data endpoints are accessible
    Check if REST API endpoints for LearnPress course enrollment exist (typically /wp-json/lp/v1/courses/{course_id}/enrollment or similar), or inspect the plugin source for enrollment-related REST routes
    Affected if LearnPress REST API endpoints for enrollment data are registered and publicly accessible to authenticated users
  5. Test for IDOR on userId parameter
    Using an authenticated subscriber account, make a request to the enrollment endpoint with a modified userId value pointing to an instructor or administrator user ID, observe if sensitive course completion or progress data is returned
    Affected if Request returns enrollment data for a user different from the authenticated subscriber without proper authorization

A site is affected if LearnPress is installed with a version below 4.3.9.2 and the plugin exposes REST API endpoints that allow any authenticated subscriber to retrieve enrollment data for other users by manipulating the userId parameter.

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

Update LearnPress to version 4.3.9.2 or later which includes proper authorization validation on the userId parameter, or implement role-based access control checks before returning enrollment data.

Recommended fix Moderate confidence

4.3.10 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the LearnPress plugin
  4. 4. Check the current version number (should be 4.3.9.1 or lower if vulnerable)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful by confirming the new version number after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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