External risk intelligence

FreshRSS Admin Account Creation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-54875

FreshRSS is a self-hosted web application. While deployment varies, it is commonly exposed to the internet to allow remote access to aggregated feeds. Since the vulnerability involves user registration functionality, which is often enabled on web-accessible instances, the attack surface is frequently reachable via the internet.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in FreshRSS, a self-hosted RSS aggregator, that could allow an unprivileged attacker to create a new administrator user if registration is enabled. This could potentially lead to unauthorized control over the application. The main concern is confirming relevance and exposure of this type of self-hosted application within the organization.

  • Unprivileged users can gain admin access.
  • Critical access granted without proper controls.
  • Confirm if self-hosted RSS feeds are in use.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can gain administrative access to a FreshRSS instance by exploiting a flaw in the user registration process. If registration is enabled, the attacker can create a new administrator account by manipulating a hidden field during user creation, leading to full control of the instance.

  • Registration must be enabled.
  • Create an admin user via a hidden field.
  • Complete takeover of the instance.

Live Threat

Current exploitation, exposure, and threat context

An unprivileged attacker could create a new administrator user on a FreshRSS instance when registration is enabled. This could allow them to gain administrative control over the application.

  • Affected asset: FreshRSS administrator account.
  • Exposure: Exploiting a hidden field during user registration.
  • Consequence: Unauthorized administrative control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The FreshRSS application owner or the platform team responsible for its deployment should lead the remediation efforts. The first step is to inventory all FreshRSS instances, confirm if the registration feature is enabled, and assess business criticality and internet reachability. Once ownership and exposure are confirmed, a risk-based remediation plan, potentially involving vendor coordination or temporary risk reduction, can be developed.

  • Identify FreshRSS instance owners.
  • Verify registration feature and exposure.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is FreshRSS?

FreshRSS is a free, self-hosted web application used to aggregate RSS feeds. Users install it on their own servers to manage and read news from various websites in one centralized location.

What does CWE-284 mean for CVE-2025-54875?

CWE-284 refers to Improper Access Control. In this specific vulnerability, it means the application fails to restrict the ability to create accounts with administrative privileges, allowing an attacker to bypass intended authorization checks.

How can an attacker trigger this vulnerability?

An attacker can trigger this flaw during the user registration process by manipulating a hidden field intended only for administrative use. This vulnerability does not exist if the user registration feature is disabled on the instance.

Is my FreshRSS instance at risk?

According to Halo Surface Signal, risk depends on accessibility; if your instance is internet-facing and has user registration enabled, it is reachable. You should evaluate if your deployment allows public sign-ups.

How do I secure my FreshRSS installation?

You should verify if registration is enabled on your instances and plan an update to version 1.27.0 or later. Prioritize this for instances that are accessible over the internet.

References