# CVE-2025-69634: Cross-site request forgery in n/a

> A CSRF vulnerability in Dolibarr allows privilege escalation via the notes field, though exploitation requires knowledge of an admin token.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 14 Feb 2026
- **Also known as:** GHSA-hfj8-gv3c-fx7w

## What is CVE-2025-69634?

CVE-2025-69634 is a critical vulnerability in n/a, published on 12 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross Site Request Forgery vulnerability in Dolibarr ERP & CRM v.22.0.9 allows a remote attacker to escalate privileges via the notes field in perms.php NOTE: this is disputed by a third party who indicates that exploitation can only occur if an unprivileged user knows the token of an admin user.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String), CWE-352 (Cross-Site Request Forgery), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-69634 being exploited?

There is no known exploitation of CVE-2025-69634 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69634 is a critical vulnerability in n/a, published on 12 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-69634 in the wild and no public exploit code.

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

## Sources

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

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