{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:bugsink:bugsink:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "97568C00-5B15-484D-B081-39D276B6F579",
              "versionEndExcluding": "2.0.13",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Bugsink is a self-hosted error tracking tool. In versions prior to 2.0.13, an unauthenticated attacker who can submit events to a Bugsink project can store arbitrary JavaScript in an event. The payload executes only if a user explicitly views the affected Stacktrace in the web UI. When Pygments returns more lines than it was given (a known upstream quirk that triggers with Ruby heredoc-style input), `_pygmentize_lines()` in `theme/templatetags/issues.py:75-77` falls back to returning the raw input lines. `mark_safe()` at line 111-113 is then applied unconditionally - including to those unsanitized raw lines. Since DSN endpoints are public by Sentry protocol, no account is needed to inject. The payload sits in the database until an admin looks at the event. Successful exploitation requires that the attacker to be able to submit events to the project (i.e. knows the DSN or can access a client that uses it), the Bugsink ingest endpoint is reachable to the attacker, and an administrator explicitly views the crafted event in the UI. Under those conditions, the attacker can execute JavaScript in the administrator\u2019s browser and act with that user\u2019s privileges within Bugsink. Version 2.0.13 fixes the vulnerability."
    },
    {
      "lang": "es",
      "value": "Bugsink es una herramienta de seguimiento de errores autoalojada. En versiones anteriores a la 2.0.13, un atacante no autenticado que puede enviar eventos a un proyecto de Bugsink puede almacenar JavaScript arbitrario en un evento. La carga \u00fatil se ejecuta solo si un usuario ve expl\u00edcitamente el Stacktrace afectado en la interfaz de usuario web. Cuando Pygments devuelve m\u00e1s l\u00edneas de las que se le dieron (una peculiaridad conocida de la fuente que se activa con entrada de estilo heredoc de Ruby), \u0027_pygmentize_lines()\u0027 en \u0027theme/templatetags/issues.py:75-77\u0027 recurre a devolver las l\u00edneas de entrada sin procesar. \u0027mark_safe()\u0027 en las l\u00edneas 111-113 se aplica entonces incondicionalmente, incluso a esas l\u00edneas sin procesar no saneadas. Dado que los endpoints DSN son p\u00fablicos seg\u00fan el protocolo Sentry, no se necesita una cuenta para inyectar. La carga \u00fatil permanece en la base de datos hasta que un administrador mira el evento. Para explotarlo con \u00e9xito es preciso que el atacante pueda enviar eventos al proyecto (es decir, conozca el DSN o pueda acceder a un cliente que lo use), que el punto final de ingesta de Bugsink sea accesible para el atacante, y que un administrador vea expl\u00edcitamente el evento manipulado en la interfaz de usuario. Bajo esas condiciones, el atacante puede ejecutar JavaScript en el navegador del administrador y actuar con los privilegios de ese usuario dentro de Bugsink. La versi\u00f3n 2.0.13 corrige la vulnerabilidad."
    }
  ],
  "id": "CVE-2026-27614",
  "lastModified": "2026-02-27T19:06:26.467",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 9.3,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 5.8,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 6.1,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 2.7,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2026-02-25T03:16:05.803",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/bugsink/bugsink/commit/e784d6aeb0d5f29b40c2779d2544c2b9ef097ee9"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Product",
        "Release Notes"
      ],
      "url": "https://github.com/bugsink/bugsink/releases/tag/2.0.13"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "url": "https://github.com/bugsink/bugsink/security/advisories/GHSA-vp6q-7m36-pq3w"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-79"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}