CVE-2026-27449

{
  "id": "CVE-2026-27449",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-27449",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-03-03T01:40:06.862571Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.5,
          "attackVector": "NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "integrityImpact": "NONE",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "umbraco",
          "product": "Umbraco.Engage.Forms",
          "versions": [
            {
              "status": "affected",
              "version": "< 16.2.1"
            },
            {
              "status": "affected",
              "version": ">= 17.0.0, < 17.1.1"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-02-26T22:20:47.960",
  "references": [
    {
      "url": "https://github.com/umbraco/Umbraco.Engage.Issues/security/advisories/GHSA-86vq-ccwf-rm62",
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-284"
        },
        {
          "lang": "en",
          "value": "CWE-306"
        },
        {
          "lang": "en",
          "value": "CWE-639"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Umbraco Engage is a business intelligence platform. A vulnerability has been identified in Umbraco Engage prior to versions 16.2.1 and 17.1.1 where certain API endpoints are exposed without enforcing authentication or authorization checks. The affected endpoints can be accessed directly over the network without requiring a valid session or user credentials. By supplying a user-controlled identifier parameter (e.g., ?id=), an attacker can retrieve sensitive data associated with arbitrary records. Because no access control validation is performed, the endpoints are vulnerable to enumeration attacks, allowing attackers to iterate over identifiers and extract data at scale. An unauthenticated attacker can retrieve sensitive Engage-related data by directly querying the affected API endpoints. The vulnerability allows arbitrary record access through predictable or enumerable identifiers. The confidentiality impact is considered high. No direct integrity or availability impact has been identified. The scope of exposed data depends on the deployment but may include analytics data, tracking data, customer-related information, or other Engage-managed content. The vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1. No known workarounds are available."
    },
    {
      "lang": "es",
      "value": "Umbraco Engage es una plataforma de inteligencia de negocios. Una vulnerabilidad ha sido identificada en Umbraco Engage en versiones anteriores a la 16.2.1 y 17.1.1 donde ciertos endpoints de la API están expuestos sin aplicar comprobaciones de autenticación o autorización. Los endpoints afectados pueden ser accedidos directamente a través de la red sin requerir una sesión válida o credenciales de usuario. Al proporcionar un parámetro identificador controlado por el usuario (por ejemplo, ?id=), un atacante puede recuperar datos sensibles asociados con registros arbitrarios. Debido a que no se realiza ninguna validación de control de acceso, los endpoints son vulnerables a ataques de enumeración, permitiendo a los atacantes iterar sobre identificadores y extraer datos a escala. Un atacante no autenticado puede recuperar datos sensibles relacionados con Engage consultando directamente los endpoints de la API afectados. La vulnerabilidad permite el acceso arbitrario a registros a través de identificadores predecibles o enumerables. El impacto en la confidencialidad se considera alto. No se ha identificado ningún impacto directo en la integridad o disponibilidad. El alcance de los datos expuestos depende de la implementación, pero puede incluir datos analíticos, datos de seguimiento, información relacionada con clientes u otro contenido gestionado por Engage. La vulnerabilidad afecta tanto a la v16 como a la v17. Los parches ya han sido lanzados. Se aconseja a los usuarios actualizar a la 16.2.1 o 17.1.1. No se conocen soluciones alternativas disponibles."
    }
  ],
  "lastModified": "2026-06-17T10:27:10.683",
  "sourceIdentifier": "security-advisories@github.com"
}