dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-22739

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-27
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
Missing Authorization vulnerability in ThimPress LearnPress learnpress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LearnPress: from n/a through <= 4.2.7.5.

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

Missing Authorization vulnerability in LearnPress WordPress plugin allows unauthenticated attackers to access functionality or data that should require proper authorization due to incorrectly configured access control security levels. The vulnerability exists in versions through 4.2.7.5 and can be exploited over the network.

MitigationUpdate LearnPress to the latest patched version beyond 4.2.7.5. Verify that the update properly enforces authorization checks on all sensitive endpoints and functionality.

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
    In WordPress admin, go to Plugins > Installed Plugins and look for LearnPress in the list. Alternatively, check the /wp-content/plugins directory for a learnpress folder.
    Affected if The LearnPress plugin is present in the WordPress installation
  2. Identify installed LearnPress version
    In WordPress admin, go to Plugins > Installed Plugins and locate LearnPress - the version number is displayed below the plugin name. Alternatively, check the version in the main plugin file header at /wp-content/plugins/learnpress/readme.txt or in the plugin's main PHP file.
    Affected if Version is 4.2.7.5 or lower (any version through 4.2.7.5)
  3. Test for unauthenticated access to admin functionality
    Attempt to access WordPress admin URLs without logging in, such as /wp-admin/admin.php?page=learnpress or direct requests to LearnPress AJAX endpoints (admin-ajax.php?action=lp_*) while logged out. Use a tool like curl or Burp Suite to send unauthenticated requests.
    Affected if The server responds with any LearnPress data or success messages instead of redirecting to login or returning an authorization error
  4. Inspect LearnPress endpoint access controls
    Review the LearnPress plugin files (particularly in /inc/ and /includes/ directories) for AJAX action handlers and admin page access. Look for functions that handle sensitive operations (user data, course management, order processing) and verify if they check current_user_can() or is_user_logged_in() before executing.
    Affected if Sensitive functions lack proper capability checks or login verification

A defender is affected if LearnPress is installed and the version is 4.2.7.5 or lower, AND unauthenticated requests can access LearnPress functionality that should require authorization.

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 the latest patched version beyond 4.2.7.5. Verify that the update properly enforces authorization checks on all sensitive endpoints and functionality.

Recommended fix Moderate confidence

Latest LearnPress version available (beyond 4.2.7.5)

  1. 1. Check current LearnPress plugin version installed on your WordPress site
  2. 2. If version is <= 4.2.7.5, backup your WordPress database and files before updating
  3. 3. Update LearnPress plugin to the latest available version from the WordPress plugin repository or ThimPress
  4. 4. Verify the update was successful and test critical LearnPress functionality (course enrollment, admin access controls)
  5. 5. Review user roles and permissions in WordPress to ensure proper access controls are in place

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