CVE-2025-54425

{"id": "CVE-2025-54425", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2025-07-30T14:15:29.073", "references": [{"url": "https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api", "source": "security-advisories@github.com"}, {"url": "https://github.com/umbraco/Umbraco-CMS/commit/7e82c258eebaa595eadc9b000461e27d02bc030e", "source": "security-advisories@github.com"}, {"url": "https://github.com/umbraco/Umbraco-CMS/commit/9f37db18d11c8ba4e3ecdeb35291af30ebee7cd0", "source": "security-advisories@github.com"}, {"url": "https://github.com/umbraco/Umbraco-CMS/commit/da43086017e1e318f6b5373391d78421efebce3a", "source": "security-advisories@github.com"}, {"url": "https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-75vq-qvhr-7ffr", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-200"}]}], "descriptions": [{"lang": "en", "value": "Umbraco is an ASP.NET CMS. In versions 13.0.0 through 13.9.2, 15.0.0 through 15.4.1 and 16.0.0 through 16.1.0, the content delivery API can be restricted from public access where an API key must be provided in a header to authorize the request. It's also possible to configure output caching, such that the delivery API outputs will be cached for a period of time, improving performance. There's an issue when these two things are used together, where caching doesn't vary by the header that contains the API key. As such, it's possible for a user without a valid API key to retrieve a response for a given path and query if it has recently been requested and cached by request with a valid key. This is fixed in versions 13.9.3, 15.4.4 and 16.1.1."}, {"lang": "es", "value": "Umbraco es un CMS ASP.NET. En las versiones 13.0.0 a 13.9.2, 15.0.0 a 15.4.1 y 16.0.0 a 16.1.0, se puede restringir el acceso p\u00fablico a la API de entrega de contenido, donde se debe proporcionar una clave de API en un encabezado para autorizar la solicitud. Tambi\u00e9n es posible configurar el almacenamiento en cach\u00e9 de salida, de modo que las salidas de la API de entrega se almacenen en cach\u00e9 durante un per\u00edodo, lo que mejora el rendimiento. Existe un problema cuando se utilizan estas dos opciones juntas: el almacenamiento en cach\u00e9 no var\u00eda seg\u00fan el encabezado que contiene la clave de API. Por lo tanto, es posible que un usuario sin una clave de API v\u00e1lida recupere una respuesta para una ruta y consulta determinadas si se ha solicitado recientemente y se ha almacenado en cach\u00e9 mediante una solicitud con una clave v\u00e1lida. Esto se solucion\u00f3 en las versiones 13.9.3, 15.4.4 y 16.1.1."}], "lastModified": "2025-07-31T18:42:37.870", "sourceIdentifier": "security-advisories@github.com"}