# CVE-2019-25367: ArangoDB Community Edition 3.4.2-1 XSS via aardvark admin interface

> Attackers can inject malicious scripts into the ArangoDB Aardvark admin interface, allowing JavaScript execution in authenticated users' browsers.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **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:** 15 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-2wpq-gf9v-758w

## What is CVE-2019-25367?

CVE-2019-25367 is a medium-severity cross-site scripting vulnerability in ArangoDB Community Edition, published on 15 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

ArangoDB Community Edition 3.4.2-1 contains multiple cross-site scripting vulnerabilities in the Aardvark web admin interface (index.html) through search, user management, and API parameters. Attackers can inject scripts via parameters in /_db/_system/_admin/aardvark/index.html to execute JavaScript in authenticated users' browsers.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2019-25367 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25367 is a medium-severity cross-site scripting vulnerability in ArangoDB Community Edition, published on 15 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25367 exists.

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

## Sources

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

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