Shared favicon replacement via incomplete cache key
Published Jun 4, 2025 · Updated Jun 4, 2025
Cache poisoning in FreshRSS before 1.26.2 allows remote authenticated users to replace feed favicons for all users. The FreshRSS_Feed::hash method keys shared favicon files only on the feed URL and system salt, omitting the mutable website URL and proxy settings used to fetch the image. Any account can edit a feed website URL or intercept its response through a configured proxy, causing attacker-controlled imagery to appear across accounts.
Summary
What happened
Cache poisoning in FreshRSS before 1.26.2 allows remote authenticated users to replace feed favicons for all users. The FreshRSS_Feed::hash method keys shared favicon files only on the feed URL and system salt, omitting the mutable website URL and proxy settings used to fetch the image. Any account can edit a feed website URL or intercept its response through a configured proxy, causing attacker-controlled imagery to appear across accounts.
The record
- CVE
- CVE-2025-46339
- Published
- Jun 4, 2025
- Updated
- Jun 4, 2025
- Vendor
- FreshRSS
- Product
- FreshRSS
- Classifications
- CWE-349, T1491.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2025CVE publishedPublication date reported by the CVE source.
- Jun 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.26.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream favicon cache-poisoning proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo