# CVE-2025-27792: Opal vulnerable to CSRF protection bypass

> Attackers can bypass CSRF protections in Opal by dropping the referrer header, allowing unauthorized actions on behalf of authenticated users.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** AZL-62429, GHSA-27vw-29rq-c358

## What is CVE-2025-27792?

CVE-2025-27792 is a high-severity vulnerability in obiba opal, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Opal is OBiBa’s core database application for biobanks or epidemiological studies. Prior to version 5.1.1, the protections against cross-site request forgery (CSRF) were insufficient application-wide. The referrer header is checked, and if it is invalid, the server returns 403. However, the referrer header can be dropped from CSRF requests using `<meta name="referrer" content="never">`, effectively bypassing this protection. Version 5.1.1 contains a patch for the issue.

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

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


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

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

## Is CVE-2025-27792 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27792 is a high-severity vulnerability in obiba opal, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27792 exists.

Affected product: obiba opal. 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-27792/ (Markdown: https://insights.sbomify.com/CVE-2025-27792/index.md)
```

## Sources

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

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