dbcve.org
AlfApplication

CVE-2024-25628

HIGH · 7.6 CVSS v3.1 Published 2024-02-16
Fix available
A fix is available. Upgrade to 2.0-m4-2402 or later.
See remediation →
82/100
Remediation priority · High
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
Alf.io is a free and open source event attendance management system. In versions prior to 2.0-M4-2402 users can access the admin area even after being invalidated/deleted. This issue has been addressed in version 2.0-M4-2402. All users are advised to upgrade. There are no known workarounds for this vulnerability.

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

Alf.io versions prior to 2.0-M4-2402 contain an authentication bypass where invalidated or deleted users retain functional access to the admin area due to improper session invalidation upon user status changes.

MitigationUpgrade to version 2.0-M4-2402; no workarounds exist.

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
AlfApplication
Affected:< 2.0-m4-2402

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

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

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 Alf.io version
    Locate the Alf.io application files and check the version identifier in the build configuration, manifest, or version file. Common locations include the WAR file properties, a version.txt file, or the admin dashboard version display.
    Affected if The installed version is anything prior to 2.0-m4-2402 (e.g., 2.0-m4-2309, 2.0-m3-xxx, etc.)
  2. Inspect user database for disabled accounts
    Query the users table in the Alf.io database to identify accounts where the status field indicates deletion, suspension, or invalidation. Check for flags such as deleted=true, enabled=false, or similar status columns.
    Affected if There exist user records marked as deleted, disabled, or invalidated who may still have active sessions in the session store.
  3. Review active session records
    Examine the session storage mechanism (database table or file-based sessions) to identify sessions currently associated with user IDs. Cross-reference with the user status findings from step 2.
    Affected if Sessions exist for users whose account status is deleted, disabled, or invalidated in the user table.
  4. Verify session invalidation behavior
    Create a test admin user, then modify that user's status to disabled or deleted. Attempt to access the admin area using an existing session cookie or token without re-authenticating.
    Affected if The session remains valid after the user account is disabled or deleted, allowing continued access to admin functionality.

You are affected if running any Alf.io version prior to 2.0-m4-2402 and there exist sessions from users whose accounts have been invalidated or deleted that still provide admin area access.

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 2.0-m4-2402 or later
Fixed in 2.0-m4-2402
Interim mitigation

Upgrade to version 2.0-M4-2402; no workarounds exist.

Recommended fix High confidence

2.0-M4-2402

  1. Download Alf.io version 2.0-M4-2402 from the official GitHub releases or repository
  2. Backup the existing database and application configuration
  3. Stop the currently running Alf.io instance
  4. Replace the application files with the new version
  5. Ensure database migrations are run if required by the upgrade
  6. Restart the Alf.io service
  7. Verify that invalidated/deleted users can no longer access the admin area

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

Fix this in Alf 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-2024-25628 — 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-2024-25628 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