CVE-2025-52968
xdg-open in xdg-utils through 1.2.1 can send requests containing SameSite=Strict cookies, which can facilitate CSRF. (For example, xdg-open could be modified to, by default, associate x-scheme-handler/https with the execution of a browser with command-line options that arrange for an empty cookie store, although this would add substantial complexity, and would not be considered a desirable or expected behavior by all users.) NOTE: this is disputed because integrations of xdg-open typically do not provide information about whether the xdg-open command and arguments were manually entered by a user, or whether they were the result of a navigation from content in an untrusted origin.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
- Puntuación base: 2.7
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.21%
- Percentil entre todas las CVEs puntuadas: 10
- Fecha de la puntuación: 5/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
CWE
- CWE-420
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2025-52968",
"cveTags": [
{
"tags": [
"disputed"
],
"sourceIdentifier": "cve@mitre.org"
}
],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-52968",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2025-06-23T15:37:38.295673Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "cve@mitre.org",
"cvssData": {
"scope": "CHANGED",
"version": "3.1",
"baseScore": 2.7,
"attackVector": "LOCAL",
"baseSeverity": "LOW",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N",
"integrityImpact": "NONE",
"userInteraction": "REQUIRED",
"attackComplexity": "HIGH",
"availabilityImpact": "NONE",
"privilegesRequired": "NONE",
"confidentialityImpact": "LOW"
},
"impactScore": 1.4,
"exploitabilityScore": 1
}
]
},
"affected": [
{
"source": "cve@mitre.org",
"affectedData": [
{
"vendor": "freedesktop",
"product": "xdg-utils",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "semver",
"lessThanOrEqual": "1.2.1"
}
],
"defaultStatus": "unknown"
}
]
}
],
"published": "2025-06-23T15:15:29.350",
"references": [
{
"url": "https://cgit.freedesktop.org/xdg/xdg-utils/tag/?h=v1.2.1",
"source": "cve@mitre.org"
},
{
"url": "https://www.openwall.com/lists/oss-security/2025/06/23/1",
"source": "cve@mitre.org"
}
],
"vulnStatus": "Deferred",
"weaknesses": [
{
"type": "Secondary",
"source": "cve@mitre.org",
"description": [
{
"lang": "en",
"value": "CWE-420"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "xdg-open in xdg-utils through 1.2.1 can send requests containing SameSite=Strict cookies, which can facilitate CSRF. (For example, xdg-open could be modified to, by default, associate x-scheme-handler/https with the execution of a browser with command-line options that arrange for an empty cookie store, although this would add substantial complexity, and would not be considered a desirable or expected behavior by all users.) NOTE: this is disputed because integrations of xdg-open typically do not provide information about whether the xdg-open command and arguments were manually entered by a user, or whether they were the result of a navigation from content in an untrusted origin."
},
{
"lang": "es",
"value": "xdg-open en xdg-utils hasta la versión 1.2.1 puede enviar solicitudes que contienen cookies SameSite=Strict, lo que facilita el CSRF. (Por ejemplo, xdg-open podría modificarse para asociar, por defecto, x-scheme-handler/https con la ejecución de un navegador con opciones de línea de comandos que gestionen un almacén de cookies vacío, aunque esto añadiría una complejidad considerable y no sería considerado un comportamiento deseable ni esperado por todos los usuarios). NOTA: Esto es controvertido porque las integraciones de xdg-open no suelen proporcionar información sobre si el comando y los argumentos de xdg-open fueron introducidos manualmente por un usuario o si fueron el resultado de una navegación desde contenido de un origen no confiable."
}
],
"lastModified": "2026-06-17T09:37:21.183",
"sourceIdentifier": "cve@mitre.org"
}