dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-11368

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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 LMS Plugin plugin for WordPress is vulnerable to Sensitive Information Disclosure in all versions up to, and including, 4.2.9.4. This is due to missing capability checks in the REST endpoint /wp-json/lp/v1/load_content_via_ajax which allows arbitrary callback execution of admin-only template methods. This makes it possible for unauthenticated attackers to retrieve admin curriculum HTML, quiz questions with correct answers, course materials, and other sensitive educational content via the REST API endpoint granted they can supply valid numeric IDs.

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 enforce authorization checks on the REST endpoint /wp-json/lp/v1/load_content_via_ajax, allowing unauthenticated attackers to invoke admin-only template callbacks. By supplying valid numeric IDs (course, lesson, quiz IDs), attackers can exfiltrate sensitive educational content including curriculum HTML, quiz questions with correct answers, and course materials.

MitigationUpdate LearnPress to version 4.2.9.5 or later which implements proper capability checks on the vulnerable REST endpoint. Until updated, consider restricting access to the /wp-json/lp/v1/ endpoint via firewall rules.

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. Verify LearnPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for LearnPress, or check the file /wp-content/plugins/learnpress for existence
    Affected if LearnPress plugin is present on the WordPress site
  2. Check installed LearnPress version
    Look in the LearnPress plugin header (version field) or query the database: SELECT option_value FROM wp_options WHERE option_name = 'learnpress_version'
    Affected if Version is present and less than 4.2.9.5
  3. Test if the vulnerable REST endpoint responds to unauthenticated requests
    Send a GET request to /wp-json/lp/v1/load_content_via_ajax without authentication credentials, or with an invalid/non-existent course ID parameter
    Affected if The endpoint returns an HTTP 200 response instead of 401/403 authentication error
  4. Verify the endpoint returns sensitive content without authorization
    If the endpoint responds, check if it returns lesson content, quiz questions, or course curriculum data when supplied with valid numeric IDs without providing valid authentication
    Affected if Content including lesson HTML, quiz questions, or course materials is returned to unauthenticated users

A site is affected if LearnPress version is below 4.2.9.5 and the /wp-json/lp/v1/load_content_via_ajax endpoint returns course, lesson, or quiz content to unauthenticated requests.

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.2.9.5 or later which implements proper capability checks on the vulnerable REST endpoint. Until updated, consider restricting access to the /wp-json/lp/v1/ endpoint via firewall rules.

Recommended fix High confidence

LearnPress version 4.2.9.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the LearnPress plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.2.9.5 or later
  5. 5. After updating, verify the plugin version shows 4.2.9.5 or higher under Plugins > Installed Plugins
  6. 6. Test that the /wp-json/lp/v1/load_content_via_ajax endpoint no longer returns sensitive data to unauthenticated users

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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