CVE-2026-31832

{"id": "CVE-2026-31832", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.4, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 2.5, "exploitabilityScore": 2.8}]}, "published": "2026-03-10T22:16:21.257", "references": [{"url": "https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-fpvf-fvp5-996r", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-639"}]}], "descriptions": [{"lang": "en", "value": "Umbraco is an ASP.NET CMS. From 14.0.0 to before 16.5.1 and 17.2.2, A broken object-level authorization vulnerability exists in a backoffice API endpoint that allows authenticated users to assign domain-related data to content nodes without proper authorization checks. The issue is caused by insufficient authorization enforcement on the affected API endpoint, whereby via an API call, domains can be set on content nodes that the editor does not have permission to access (either via user group privileges or start nodes). This vulnerability is fixed in 16.5.1 and 17.2.2."}, {"lang": "es", "value": "Umbraco es un CMS de ASP.NET. Desde la versi\u00f3n 14.0.0 hasta antes de la 16.5.1 y la 17.2.2, existe una vulnerabilidad de autorizaci\u00f3n a nivel de objeto rota en un endpoint de API del backoffice que permite a usuarios autenticados asignar datos relacionados con dominios a nodos de contenido sin las comprobaciones de autorizaci\u00f3n adecuadas. El problema es causado por una aplicaci\u00f3n de autorizaci\u00f3n insuficiente en el endpoint de API afectado, por la cual, a trav\u00e9s de una llamada a la API, se pueden establecer dominios en nodos de contenido a los que el editor no tiene permiso para acceder (ya sea a trav\u00e9s de privilegios de grupo de usuarios o nodos de inicio). Esta vulnerabilidad est\u00e1 corregida en la 16.5.1 y la 17.2.2."}], "lastModified": "2026-03-11T13:52:47.683", "sourceIdentifier": "security-advisories@github.com"}