dbcve.org
FreshrssApplication

CVE-2025-68932

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-27
Fix available
A fix is available. Upgrade to 1.28.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. Prior to version 1.28.0, FreshRSS uses cryptographically weak random number generators (mt_rand() and uniqid()) to generate remember-me authentication tokens and challenge-response nonces. This allows attackers to predict valid session tokens, leading to account takeover through persistent session hijacking. The remember-me tokens provide permanent authentication and are the sole credential for "keep me logged in" functionality. This issue has been patched in version 1.28.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 prior to 1.28.0 use cryptographically weak random number generators (mt_rand() and uniqid()) to generate remember-me authentication tokens and challenge-response nonces. Attackers can predict these tokens due to the deterministic nature of these functions, enabling persistent session hijacking and complete account takeover through the 'keep me logged in' functionality.

MitigationUpgrade to FreshRSS version 1.28.0 or later which implements cryptographically secure random token generation. If immediate upgrade is not feasible, disable the 'keep me logged in' functionality as a temporary mitigation.

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.28.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. Identify FreshRSS version
    Locate the version file or check the admin interface for the current FreshRSS version number. Common locations include a VERSION file in the installation directory or the About section in the dashboard.
    Affected if The installed version is any release prior to 1.28.0 (for example, 1.27.x, 1.26.x, or older).
  2. Confirm 'keep me logged in' functionality is in use
    Check whether the remember-me or persistent login feature is enabled in the FreshRSS authentication settings or user preferences. This is typically found in the configuration panel under security or login settings.
    Affected if The 'keep me logged in', 'remember me', or persistent session feature is currently active or has been used by any user account.
  3. Inspect authentication token generation code
    Search the FreshRSS source code for the presence of mt_rand() or uniqid() functions being used in files related to authentication, session management, or token generation (for example, files handling remember-me cookies or login tokens).
    Affected if The code uses mt_rand() or uniqid() to generate remember-me tokens or security nonces instead of cryptographically secure random functions like random_bytes() or openssl_random_pseudo_bytes().
  4. Review cookie or token storage
    If accessible, examine the cookies or token data stored for the remember-me feature. Check if the token format appears predictable or if tokens follow a simple pattern that could be enumerated.
    Affected if Tokens appear short, numeric, or follow a predictable pattern consistent with mt_rand() or uniqid() output rather than a long random hex or base64 string.

You are affected if your FreshRSS installation is any version before 1.28.0 and the 'keep me logged in' feature is enabled, as weak random number generation makes authentication tokens predictable.

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

Upgrade to FreshRSS version 1.28.0 or later which implements cryptographically secure random token generation. If immediate upgrade is not feasible, disable the 'keep me logged in' functionality as a temporary mitigation.

Recommended fix High confidence

1.28.0

  1. Upgrade FreshRSS to version 1.28.0 or later
  2. After upgrading, users may need to log in again as existing remember-me tokens generated with the weak PRNG should be invalidated
Caveat Minimal - users will need to re-authenticate as weak tokens are invalidated

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
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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