CVE-2025-31482VulnerabilityPublished 4 Jun 2025

CVE-2025-31482: FreshRSS · Cross-Site Request Forgery (CSRF)

Affects FreshRSSSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.26.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.26.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade freshrss/FreshRSS to 1.26.2.

Affected software

Product	Affected	Fixed in
GitHubfreshrss/FreshRSS`pkg:github/freshrss/FreshRSS`Other threats	Affected <1.26.2	Fixed in 1.26.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify the version of FreshRSS deployed and upgrade to version 1.26.2 or later, where the vulnerability is patched. Since the vulnerability exploits CSRF, administrators should ensure that CSRF protections are enabled and properly configured in their FreshRSS installations. This includes validating anti-CSRF tokens on state-changing requests and ensuring that feed fetching mechanisms do not process untrusted or unauthenticated feed entries without validation. User education is also important: users should be cautioned against subscribing to unknown or untrusted RSS feeds. Network-level controls can be implemented to restrict access to known safe feed sources or to monitor for unusual feed subscription patterns. For organizations hosting FreshRSS publicly, implementing Web Application Firewalls (WAFs) with rules to detect and block CSRF attempts can provide additional protection. Regular security audits and monitoring for unusual logout patterns can help detect exploitation attempts early. Finally, maintaining an up-to-date inventory of self-hosted applications and applying patches promptly is critical to reduce exposure.

Description

FreshRSS is a self-hosted RSS feed aggregator. A vulnerability in versions prior to 1.26.2 causes a user to be repeatedly logged out after fetching a malicious feed entry, effectively causing that user to suffer denial of service. Version 1.26.2 contains a patch for the issue.

Impact

For European organizations using FreshRSS for internal or public RSS feed aggregation, this vulnerability can cause significant disruption to user productivity by forcing repeated logouts and denying access to the aggregator service. Although the impact is limited to availability and does not compromise data confidentiality or integrity, the denial of service can affect workflows that rely on timely access to aggregated news or information feeds. Organizations with multiple users depending on FreshRSS may experience widespread inconvenience and potential operational delays. Since FreshRSS is often self-hosted, organizations with less mature patch management processes may remain vulnerable for extended periods. Additionally, sectors that rely heavily on continuous information flow, such as media, research institutions, and government agencies, could see a degradation in service quality. The requirement for user interaction means that social engineering or user awareness is a factor, but the vulnerability could be exploited via malicious feed subscriptions or links. The absence of known exploits in the wild reduces immediate risk, but the medium severity score and ease of exploitation warrant proactive mitigation.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/FreshRSS/FreshRSS/security/advisories/GHSA-vpmc-3fv2-jmgp (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2025, 19:58 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats