dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-8383

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 plugin before 4.3.7 does not gate the `edit` context on one of its REST endpoint behind the `edit_users` capability, allowing unauthenticated visitors to retrieve each returned user's roles, full capabilities map, extra capabilities, locale, and registration date via a crafted request

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 · moderate confidence

The LearnPress WordPress plugin before version 4.3.7 lacks proper authorization enforcement on a REST API endpoint. The endpoint exposes the 'edit' context without verifying the user has the 'edit_users' capability, allowing unauthenticated attackers to query and retrieve sensitive user metadata including roles, capabilities, locale, and registration dates.

MitigationUpdate LearnPress to version 4.3.7 or later, which adds the required capability gate to the vulnerable REST endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 your WordPress plugins directory or access wp-admin > Plugins to verify LearnPress is active
    Affected if LearnPress is installed and active
  2. Identify the installed LearnPress version
    Navigate to wp-admin > Plugins > LearnPress and note the version number displayed, or inspect the plugin header in wp-content/plugins/learnpress/readme.txt
    Affected if Version is below 4.3.7 (e.g., 4.3.6, 4.3.5, etc.)
  3. Verify the vulnerable REST endpoint responds without authentication
    Send a GET request to /wp-json/lp/v1/users?context=edit without providing any authentication headers or cookies
    Affected if The endpoint returns HTTP 200 and includes user data such as roles, capabilities, locale, or registration dates without requiring authentication
  4. Confirm the endpoint lacks capability enforcement
    Examine the REST API response headers and body to verify no error about missing 'edit_users' capability is returned; the endpoint should return actual user metadata
    Affected if User metadata is exposed without any capability check, confirming the authorization flaw exists

You are affected if LearnPress is installed with a version before 4.3.7 and the /wp-json/lp/v1/users?context=edit endpoint returns user data without requiring authentication.

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.7 or later, which adds the required capability gate to the vulnerable REST endpoint.

Recommended fix Moderate confidence

LearnPress 4.3.7 or later

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate LearnPress in the plugin list.
  4. 4. If an update to version 4.3.7 or later is available, click 'Update Now' to install the fixed version.
  5. 5. Alternatively, you can manually update by downloading LearnPress 4.3.7 or later from the WordPress plugin repository and uploading it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the REST API endpoint no longer exposes user data to unauthenticated requests by testing with an unauthenticated request to the affected endpoint.

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-8383 — 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-8383 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