# CVE-2026-108963 — David-Crty databasement

> As of 2026-10-11, CVE-2026-108963 is a HIGH-severity vulnerability in David-Crty databasement, CVSS v3.1 8.8, EPSS 1.6% (76.3th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-108963 as of 2026-10-11; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-11

## What is CVE-2026-108963?

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.

The record classifies CVE-2026-108963 under weakness class [CWE-88](https://intel.threadlinqs.com/cwe/CWE-88). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 39 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.8 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 1.6% probability of exploitation in the next 30 days, higher than 76.3% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 7.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-11

## Is CVE-2026-108963 being exploited?

It currently carries a trending score of 49 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **David-Crty**: databasement

## How to fix CVE-2026-108963

Vendor advisory: [https://github.com/David-Crty/databasement/security/advisories/GHSA-hm57-pvxc-4pcm](https://github.com/David-Crty/databasement/security/advisories/GHSA-hm57-pvxc-4pcm). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-108963

No threat campaign in the Threadlinqs corpus currently references CVE-2026-108963, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, FIRST EPSS.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/David-Crty/databasement/security/advisories/GHSA-hm57-pvxc-4pcm)

**Issue tracking and product pages**

- [github.com — product](https://github.com/David-Crty/databasement/blob/bcee6f0e62796337aaac26961c41f7eb9578dd76/app/Services/Backup/Databases/MysqlDatabase.php#L22)

**Other references**

- [github.com](https://github.com/David-Crty/databasement/commit/2d2761905594a2fa2c3d81d48a7c8b6a1784862c)
- [github.com (22258e3eac594e653f9d04a69d93e83923d61499)](https://github.com/David-Crty/databasement/commit/22258e3eac594e653f9d04a69d93e83923d61499)
- [github.com — not applicable](https://github.com/David-Crty/databasement/blob/bcee6f0e62796337aaac26961c41f7eb9578dd76/composer.json#L3)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-108963
No Threadlinqs detection currently covers CVE-2026-108963; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
