dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-44720

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
OpenLearnX is an open-source, decentralized learning and assessment platform. Prior to 2.0.4, a critical authentication vulnerability was identified in OpenLearnX that could allow unauthorized access to user accounts under specific conditions. This vulnerability is fixed in 2.0.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

OpenLearnX versions prior to 2.0.4 contain an authentication vulnerability that allows unauthorized access to user accounts under specific conditions. This is a critical authentication bypass issue in the open-source decentralized learning platform.

MitigationUpgrade OpenLearnX to version 2.0.4 or later to remediate this authentication vulnerability.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate OpenLearnX installation
    Search for OpenLearnX directories or check installed packages on the system using commands like 'find / -name "openlearnx*"' or 'dpkg -l | grep openlearnx' or 'npm list -g openlearnx' depending on installation method
    Affected if OpenLearnX is installed on the system
  2. Determine installed version
    Run version detection command appropriate to the installation method - check for a version file, use CLI flag '--version', or inspect package.json/metadata if present
    Affected if Version cannot be determined or is returned as null/unknown
  3. Compare version to threshold
    Compare the discovered version number to 2.0.4 using semantic version comparison - any version prior to 2.0.4 (e.g., 2.0.3, 2.0.0, 1.x.x) is vulnerable
    Affected if Installed version is less than 2.0.4
  4. Verify authentication module is active
    Check if the authentication module is enabled by inspecting configuration files or running status commands for the OpenLearnX service
    Affected if Authentication module is enabled and version is below 2.0.4

User is affected if OpenLearnX is installed with a version prior to 2.0.4 and the authentication functionality is in use on the platform

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

Upgrade OpenLearnX to version 2.0.4 or later to remediate this authentication vulnerability.

Recommended fix Moderate confidence

2.0.4

  1. 1. Identify the currently installed version of OpenLearnX
  2. 2. If the current version is prior to 2.0.4, plan for upgrade to version 2.0.4
  3. 3. Review upgrade documentation for OpenLearnX
  4. 4. Perform upgrade to version 2.0.4
  5. 5. Verify the installation of version 2.0.4
  6. 6. Test authentication functionality to confirm the vulnerability is resolved

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
  • Testing3.0 h
  • Review / QA1.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-2026-44720 — 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-44720 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