dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66054

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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.9.4.

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

LearnPress plugin versions through 4.2.9.4 contain a missing authorization vulnerability that allows attackers to bypass access control checks due to incorrectly configured security levels. This could enable unauthorized users to access privileged functionality or perform actions outside their intended permissions.

MitigationImplement proper authorization checks and role-based access controls across all sensitive endpoints in LearnPress; update to the patched version once released and audit user role capabilities.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify LearnPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'LearnPress' in the list. Alternatively, check if /wp-content/plugins/learnpress/ directory exists on the server.
    Affected if LearnPress plugin is installed and active
  2. Determine installed LearnPress version
    In WordPress admin, go to Plugins > Installed Plugins > LearnPress and view the version number displayed. Or read the main plugin file (e.g., /wp-content/plugins/learnpress/learnpress.php) and look for the 'Version' header in the plugin comments.
    Affected if Version is 4.2.9.4 or lower (any version 'through 4.2.9.4')
  3. Confirm the authorization bypass is exploitable
    This vulnerability is inherent to the affected versions - it stems from incorrectly configured security levels in the plugin code that allow privilege escalation. No specific configuration toggle exists; the flaw exists in the access control logic itself.
    Affected if Running any LearnPress version through 4.2.9.4 and the site has sensitive LearnPress features enabled (courses, quizzes, user management)
  4. Audit WordPress user roles with LearnPress access
    Review which user roles (Administrator, Editor, Author, Subscriber, etc.) have access to LearnPress functionality by checking Users > Users in admin or inspecting LearnPress role capabilities in the database.
    Affected if Lower-privileged users (such as subscribers or guests) can access or modify LearnPress content they should not be able to

You are affected if LearnPress plugin version 4.2.9.4 or any lower version is installed and active on your WordPress site.

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

Implement proper authorization checks and role-based access controls across all sensitive endpoints in LearnPress; update to the patched version once released and audit user role capabilities.

Recommended fix Moderate confidence

Upgrade to a LearnPress version newer than 4.2.9.4 (latest stable release)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the LearnPress plugin in the list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the plugin version is newer than 4.2.9.4.
  6. 6. Test critical LearnPress functionality (course enrollment, admin access, user permissions) to confirm the update did not break existing features.
Caveat Minor: Review plugin settings after upgrade as some configuration options may have changed

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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