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

> Attackers can perform unauthorized actions on behalf of privileged users via crafted GET requests to the GraphQL endpoint.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-v4f8-5p2q-h868

## What is CVE-2025-15550?

CVE-2025-15550 is a medium-severity vulnerability in birkir prime, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-15550?


## How do I fix CVE-2025-15550?

No fix has been published for CVE-2025-15550 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15550 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15550 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15550 and fix it if it is affected.

What it is: CVE-2025-15550 is a medium-severity vulnerability in birkir prime, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15550 exists.

Affected product: birkir prime. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15550/ (Markdown: https://insights.sbomify.com/CVE-2025-15550/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15550
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15550
- OSV: https://osv.dev/vulnerability/CVE-2025-15550

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15550/
Summaries are generated and may contain mistakes; the official description above is the record.