dbcve.org
RollerApplication · Apache

CVE-2025-24859

HIGH · 8.8 CVSS v3.1 Published 2025-04-14
Fix available
A fix is available. Upgrade to 6.1.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A session management vulnerability exists in Apache Roller before version 6.1.5 where active user sessions are not properly invalidated after password changes. When a user's password is changed, either by the user themselves or by an administrator, existing sessions remain active and usable. This allows continued access to the application through old sessions even after password changes, potentially enabling unauthorized access if credentials were compromised. This issue affects Apache Roller versions up to and including 6.1.4. The vulnerability is fixed in Apache Roller 6.1.5 by implementing centralized session management that properly invalidates all active sessions when passwords are changed or users are disabled.

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

Apache Roller before 6.1.5 fails to invalidate active user sessions when passwords are changed or users are disabled. This session management flaw allows continued access using old sessions even after credential rotation, creating a window for unauthorized access if credentials were previously compromised.

MitigationUpgrade to Apache Roller 6.1.5 or later, which implements centralized session management that properly invalidates all active sessions upon password changes or user disablement.

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
RollerApplication
Affected:>= 1.0, < 6.1.5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Apache Roller version
    Check the Roller installation for its version number, typically found in the WAR file manifest, pom.xml, or the application's about/admin page
    Affected if Version is >= 1.0 and < 6.1.5 (vulnerable)
  2. Locate session management configuration
    Examine Roller's web.xml or Spring configuration files for session management settings, specifically looking for any session-invalidation mechanisms tied to password changes
    Affected if No session invalidation logic exists for password modifications or user disablement
  3. Review authentication filter or handler code
    Inspect the authentication-related Java classes (such as LoginAction, UserManager, or session filter implementations) to determine if password change operations trigger sessioninvalidation across all active sessions
    Affected if Password change code does not invalidate existing sessions or call a centralized session termination method
  4. Check for centralized session registry
    Look for a session tracking or registry mechanism that maintains a mapping of user IDs to active HTTP sessions, which would be required to invalidate all sessions on password change
    Affected if No centralized session registry exists to enumerate and invalidate all sessions for a given user
  5. Test session persistence after password change
    Log in as a test user, change the password via admin interface, then attempt to use the previously active session to access the application
    Affected if The old session remains valid and authenticated after password has been changed

You are affected if Apache Roller version is below 6.1.5 AND active user sessions continue to work after the user's password has been changed or the user account has been disabled.

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 6.1.5 or later
Fixed in 6.1.5
Interim mitigation

Upgrade to Apache Roller 6.1.5 or later, which implements centralized session management that properly invalidates all active sessions upon password changes or user disablement.

Recommended fix High confidence

6.1.5

  1. 1. Back up your existing Apache Roller installation and database before upgrading.
  2. 2. Download Apache Roller version 6.1.5 from the official Apache distribution repository (downloads.apache.org).
  3. 3. Stop the running Roller application server.
  4. 4. Replace the existing Roller WAR file with the new 6.1.5 WAR file in your application server's deployment directory.
  5. 5. If there are database schema changes in 6.1.5, run any provided migration scripts against your database.
  6. 6. Start the application server to deploy the upgraded Roller 6.1.5.
  7. 7. Verify that the application starts successfully and all functionalities work as expected.
  8. 8. Test that changing a user password now properly invalidates all existing sessions for that user.

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

Fix this in Roller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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