# CVE-2026-108963: Command injection in databasement

> An authenticated user can achieve remote code execution by injecting arguments into database dump commands, allowing arbitrary file writes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-7cxh-ppfp-4mq4, GHSA-hm57-pvxc-4pcm

## What is CVE-2026-108963?

CVE-2026-108963 is a high-severity command injection vulnerability in David-Crty databasement, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

databasement before 1.8.2 allows remote code execution because it runs certain commands (e.g., mariadb-dump) with a database name that can be specified by any authenticated user. For example, --result-file=/app/public/index.php can write to index.php. In other words, quoting prevents OS command injection in mariadb-dump, but the argument injection alone is sufficient for code execution indirectly. NOTE: the project's composer.json file does not indicate an independently published databasement Composer package.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-108963?


## How do I fix CVE-2026-108963?

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

## Is CVE-2026-108963 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108963 and fix it if it is affected.

What it is: CVE-2026-108963 is a high-severity command injection vulnerability in David-Crty databasement, published on 11 Oct 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-2026-108963 exists.

Affected product: David-Crty databasement. 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-2026-108963/ (Markdown: https://insights.sbomify.com/CVE-2026-108963/index.md)
```

## Sources

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

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