What is the CVSS score of CVE-2025-31482?

CVE-2025-31482 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2025-31482?

Yes, a public proof-of-concept exploit is available for CVE-2025-31482. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2025-31482?

Within 30 days: Identify affected systems running versions and apply vendor patches as part of regular patch cycle. Verify anti-CSRF tokens are enforced.

Freshrss CVE-2025-31482

Q: Which versions of Freshrss are affected by CVE-2025-31482?

Organizations using versions should be aware of moderate risk from CVE-2025-31482, a cross-site request forgery vulnerability rated CVSS 4.3.. A patch is available.

EUVD-2025-16933 MEDIUM

Cross-Site Request Forgery (CSRF) (CWE-352)

2025-06-04 security-advisories@github.com

Denial Of Service CSRF Debian Freshrss

4.3

CVSS 3.1 · GitHub Advisory

View

Vulnerability Assessment

Weakness	CWE CWE-352 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies MITRE ATT&CK 1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	An attacker can perform state-changing operations (password changes, fund transfers, data deletion) using the victim's authenticated session. With a CVSS score of 4.3 (MEDIUM), this represents a moderate risk.
Exploit ScenarioDerived	An attacker hosts a malicious page that, when visited by an authenticated user, silently submits a forged request to the target application using the user's cookies.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

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.

Earlier versions of this analysis (1)

v1 Mar 14, 2026 - 17:29 CVSS 4.3

RemediationAI

Implement anti-CSRF tokens for all state-changing operations. Use SameSite cookie attribute. Verify the Origin/Referer header on the server side.

Affected VersionsENISA

FreshRSS < 1.26.2

Affected Packages

euvd freshrss fix: 1.26.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Cross-Site Request Forgery forces authenticated users to perform unintended actions by tricking their browser into sending forged requests. This vulnerability is classified as Cross-Site Request Forgery (CSRF) (CWE-352).

Know when Freshrss gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 4.3 MEDIUM

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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

1.26.2

PoC Detected

Aug 12, 2025 - 15:21 vuln.today

Public exploit code

CVE Published

Jun 04, 2025 - 20:15 nvd

MEDIUM 4.3

Executive ViewAI

Why It Matters

Organizations using versions should be aware of moderate risk from CVE-2025-31482, a cross-site request forgery vulnerability rated CVSS 4.3. Users could be tricked into performing unintended actions. Proof-of-concept code is publicly available. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low

Compensating Controls

Apply vendor patch. If patching is delayed: implement SameSite cookie attributes and anti-CSRF tokens.

Threat Intelligence Overview

EPSS Score

0.0%

Top 86% exploitable

Exploit

POC

Public exploit code exists

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS Vendor

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity MEDIUM

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

MEDIUM severity (CVSS 4.0-6.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.