CVE-2025-57769
BaseFortify
Publication date: 2025-09-29
Last updated on: 2025-10-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| freshrss | freshrss | to 1.27.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1021 | The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with. |
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in FreshRSS versions 1.26.3 and below allows an attacker to trick a user into executing arbitrary JavaScript code or promote a user by hiding UI elements within iframes. If an authenticated iframe can be embedded, it may lead to privilege escalation by obscuring the promote user button in the admin interface or cause cross-site scripting (XSS) by tricking the user into dragging content into the UserJS text area. The issue is fixed in version 1.27.0.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute arbitrary JavaScript code in your FreshRSS instance, potentially leading to unauthorized actions such as promoting users to higher privilege levels (privilege escalation). This can compromise the security and integrity of your RSS aggregator, allowing attackers to gain administrative control or manipulate data.
What immediate steps should I take to mitigate this vulnerability?
Upgrade FreshRSS to version 1.27.0 or later, as this version contains the fix for the vulnerability. Avoid embedding authenticated iframes from untrusted sources and be cautious of user interactions that could trigger the exploit, such as dragging content into the UserJS text area.