{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46341 exists.","fix":"No fix has been published for CVE-2025-46341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46341 is a high-severity server-side request forgery vulnerability in FreshRSS, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46341 and fix it if it is affected.\n\nWhat it is: CVE-2025-46341 is a high-severity server-side request forgery vulnerability in FreshRSS, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46341 exists.\n\nAffected product: FreshRSS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46341/ (Markdown: https://insights.sbomify.com/CVE-2025-46341/index.md)","id":"CVE-2025-46341","markdown":"https://insights.sbomify.com/CVE-2025-46341/index.md","name":"CVE-2025-46341","record":{"aliases":["GHSA-w3m8-wcf4-h8vm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"RSS feed aggregator","requires_auth":"low_privilege","summary":"An attacker with an account can exploit SSRF in FreshRSS to impersonate users and escalate privileges when HTTP auth via reverse proxy is enabled.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"freshrss","vendor":"freshrss"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, when the server is using HTTP auth via reverse proxy, it's possible to impersonate any user either via the `Remote-User` header or the `X-WebAuth-User` header by making specially crafted requests via the add feed functionality and obtaining the CSRF token via XPath scraping. The attacker has to know the IP address of the proxied FreshRSS instance and the admin's username, while also having an account on the instance. An attacker can send specially crafted requests in order to gain unauthorized access to internal services. This can also lead to privilege escalation like in the demonstrated scenario, although users that have setup OIDC are not affected by privilege escalation. Version 1.26.2 contains a patch for the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Privilege escalation via SSRF when using HTTP auth","id":"CVE-2025-46341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Kyverno vulnerable to bypass of policy rules that use namespace selectors in match statements","id":"CVE-2025-46342"},"packages":[],"prev":{"headline":"Misskey CSS Style Injection Vulnerability In `MkUrlPreview`","id":"CVE-2025-46340"},"products":["FreshRSS"],"published":"2025-06-04","related":[{"cvss_score":9.8,"headline":"FreshRSS: Unauthorized creation of admin user when registration is enabled","id":"CVE-2025-54875","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":8.8,"headline":"FreshRSS has Incomplete Session Termination on Logout","id":"CVE-2025-54592","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":7.5,"headline":"FreshRSS has an IDOR which allows for viewing feeds of any user and leaking tokens","id":"CVE-2025-62166","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":7.5,"headline":"FreshRSS: Unauthenticated users can view default user's information","id":"CVE-2025-54591","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":7.4,"headline":"FreshRSS vulnerable to authenticated RCE via path traversal inside include()","id":"CVE-2025-58173","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":7.2,"headline":"FreshRSS is vulnerable to RCE attacks by authenticated admin","id":"CVE-2025-54593","kev_date_added":null,"published":"2025-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-04","vendors":["FreshRSS"]},"summary":"An attacker with an account can exploit SSRF in FreshRSS to impersonate users and escalate privileges when HTTP auth via reverse proxy is enabled.","url":"https://insights.sbomify.com/CVE-2025-46341/"}