dbcve.org
FreshrssApplication

CVE-2025-54592

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 1.27.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
FreshRSS is a free, self-hostable RSS aggregator. Versions 1.26.3 and below do not properly terminate the session during logout. After a user logs out, the session cookie remains active and unchanged. The unchanged cookie could be reused by an attacker if a new session were to be started. This failure to invalidate the session can lead to session hijacking and fixation vulnerabilities. This issue is fixed in version 1.27.0

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

FreshRSS versions 1.26.3 and below fail to invalidate the session cookie during logout. The session cookie remains active and unchanged after logout, allowing an attacker to potentially reuse the unchanged cookie if a new session begins. This creates session hijacking and session fixation attack vectors.

MitigationUpgrade FreshRSS to version 1.27.0 or later to ensure sessions are properly invalidated upon logout.

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
FreshrssApplication
Affected:< 1.27.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check FreshRSS version
    Locate the version file or check the admin dashboard for the installed FreshRSS version number
    Affected if The installed version is 1.26.3 or below (versions prior to 1.27.0)
  2. Verify session cookie behavior on logout
    Log into FreshRSS, capture the session cookie value, perform logout, then attempt to use the same cookie value in a new request
    Affected if The session cookie remains valid and unchanged after logout, allowing reuse of the old session token
  3. Inspect session invalidation code
    Examine the logout function in the FreshRSS source code for session_destroy() or session_regenerate_id() calls
    Affected if The logout function lacks proper session invalidation or does not regenerate/destroy the session ID
  4. Test session fixation vulnerability
    Obtain a session cookie before login, log in with that cookie, then log out and attempt to use the same cookie for a new session
    Affected if The original cookie remains valid after logout, enabling session fixation attacks

You are affected if your FreshRSS version is below 1.27.0 and the session cookie remains usable after performing a logout operation.

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 1.27.0 or later
Fixed in 1.27.0
Vendor patch github.com →
Interim mitigation

Upgrade FreshRSS to version 1.27.0 or later to ensure sessions are properly invalidated upon logout.

Recommended fix High confidence

1.27.0

  1. 1. Back up your FreshRSS database and all configuration files before upgrading.
  2. 2. Download FreshRSS version 1.27.0 from the official GitHub releases page: https://github.com/FreshRSS/FreshRSS/releases/tag/1.27.0
  3. 3. Extract the downloaded archive and replace all existing FreshRSS files with the new version, preserving your configuration (config.php) and data directory.
  4. 4. If using the web installer, navigate to your FreshRSS URL to complete any necessary database migrations.
  5. 5. If using the command-line interface, run the update script: `./update.py`
  6. 6. Clear your browser cookies and verify that after logging out, the session cookie is properly invalidated.
  7. 7. Log back in and confirm normal functionality is restored.

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

Fix this in Freshrss Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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