# CVE-2019-25447: OrientDB 3.0.17 Cross-Site Request Forgery

> Attackers can perform unauthorized database actions like creating users or modifying schemas via CSRF in OrientDB web interface.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-65c4-vf29-7265

## What is CVE-2019-25447?

CVE-2019-25447 is a medium-severity vulnerability in OrientDB, published on 20 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OrientDB 3.0.17 GA Community Edition contains cross-site request forgery vulnerabilities that allow attackers to perform unauthorized actions by crafting malicious requests to endpoints like /database/, /command/, and /document/. Attackers can create or delete databases, modify schema classes, manage users, and create functions by sending authenticated requests without token validation, combined with reflected and stored cross-site scripting vulnerabilities in the web interface.

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

## Which versions are affected by CVE-2019-25447?

It affects 1 product.


Products: Orientdb Orientdb.

## How do I fix CVE-2019-25447?

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

## Is CVE-2019-25447 being exploited?

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

## Other vulnerabilities in OrientDB

- [CVE-2017-11467](https://insights.sbomify.com/CVE-2017-11467/): OrientDB vulnerable to Improper Privilage Management leading to arbitrary command injection (critical 9.8)
- [CVE-2015-2912](https://insights.sbomify.com/CVE-2015-2912/): OrientDB-Server vulnerable to Cross-Site Request Forgery (high 8.8)
- [CVE-2015-2918](https://insights.sbomify.com/CVE-2015-2918/): OrientDB Studio web management interface is vulnerable to clickjacking attacks (medium 6.1)
- [CVE-2015-2913](https://insights.sbomify.com/CVE-2015-2913/): OrientDB Server Community Edition uses insufficiently random values to generate session IDs (medium 5.9)
- [CVE-2019-25448](https://insights.sbomify.com/CVE-2019-25448/): OrientDB 3.0.17 Stored Cross-Site Scripting via User Creation (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25447 and fix it if it is affected.

What it is: CVE-2019-25447 is a medium-severity vulnerability in OrientDB, published on 20 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25447 exists.

Affected product: OrientDB. 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-2019-25447/ (Markdown: https://insights.sbomify.com/CVE-2019-25447/index.md)
```

## Sources

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

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