CVE-2025-46341

{"id": "CVE-2025-46341", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 4.7, "exploitabilityScore": 1.8}]}, "published": "2025-06-04T21:15:39.937", "references": [{"url": "https://github.com/FreshRSS/FreshRSS/commit/6bb8680ae0051b9a2ff344f17814f4fa5d844628", "source": "security-advisories@github.com"}, {"url": "https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-w3m8-wcf4-h8vm", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-918"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "FreshRSS es un agregador de feeds RSS autoalojado. Antes de la versi\u00f3n 1.26.2, cuando el servidor utiliza autenticaci\u00f3n HTTP mediante proxy inverso, era posible suplantar la identidad de cualquier usuario mediante el encabezado `Remote-User` o `X-WebAuth-User`, realizando solicitudes personalizadas mediante la funci\u00f3n para agregar feeds y obteniendo el token CSRF mediante el raspado de XPath. El atacante debe conocer la direcci\u00f3n IP de la instancia de FreshRSS con proxy y el nombre de usuario del administrador, adem\u00e1s de tener una cuenta en la instancia. Un atacante puede enviar solicitudes personalizadas para obtener acceso no autorizado a servicios internos. Esto tambi\u00e9n puede provocar una escalada de privilegios, como en el caso mostrado, aunque los usuarios con OIDC configurado no se ven afectados. La versi\u00f3n 1.26.2 incluye un parche para este problema."}], "lastModified": "2025-06-05T20:12:23.777", "sourceIdentifier": "security-advisories@github.com"}