dbcve.org
Open Eclass PlatformApplication · Gunet

CVE-2026-24667

MEDIUM · 5.0 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 4.2 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable 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 Open eClass platform (formerly known as GUnet eClass) is a complete course management system. Prior to version 4.2, failure to invalidate active user sessions after a password change allows existing session tokens to remain valid, potentially enabling unauthorized continued access to user accounts. This issue has been patched in version 4.2.

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

Open eClass versions prior to 4.2 do not invalidate active user sessions when a user changes their password. This allows session tokens issued before the password change to remain valid, potentially enabling an attacker with access to those tokens (e.g., via session hijacking or shared workstations) to maintain unauthorized access even after the legitimate user changes their password.

MitigationUpgrade to Open eClass version 4.2 or later, which implements proper session invalidation on password change. Until upgraded, consider implementing additional controls such as limiting concurrent sessions or monitoring for suspicious session activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Open Eclass PlatformApplication
Affected:< 4.2

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Identify installed Open eClass version
    Locate the version file or check the admin dashboard for the current version number. Common locations include a version.php file in the root directory or the 'About' section in the administration panel.
    Affected if The installed version is below 4.2 (e.g., 4.1, 4.0, 3.x)
  2. Locate password change functionality
    Navigate to user account settings or password change page in the web interface, then examine the server-side script that handles the password update request.
    Affected if The password change script does not contain session invalidation logic (no session_destroy, session_regenerate_id, or session table cleanup)
  3. Inspect session management code
    Examine the authentication or session management module files for functions that handle password modifications and verify whether they include session token revocation.
    Affected if No session invalidation routine is called when passwords are updated
  4. Check session storage mechanism
    Review how sessions are stored (database table, files, or external) and determine if there is a mechanism to invalidate sessions by user ID when passwords change.
    Affected if Sessions are not linked to user ID for targeted invalidation, or no such invalidation occurs on password change

A user is affected if their Open eClass installation is version 4.1 or earlier and the password change function does not invalidate existing sessions.

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
Upgrade available Upgrade to 4.2 or later
Fixed in 4.2
Interim mitigation

Upgrade to Open eClass version 4.2 or later, which implements proper session invalidation on password change. Until upgraded, consider implementing additional controls such as limiting concurrent sessions or monitoring for suspicious session activity.

Recommended fix Moderate confidence

4.2

  1. 1. Back up the current Open eClass installation and database before proceeding with the upgrade
  2. 2. Download Open eClass version 4.2 from the official repository (github.com)
  3. 3. Upgrade the Open eClass installation to version 4.2
  4. 4. Verify that the session invalidation fix is properly applied by testing that user sessions are invalidated upon password change
  5. 5. Confirm the application functions normally after the upgrade

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

Fix this in Open Eclass Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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