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.
CVE-2026-108963
HIGHPre-NVD 8.88.8Trending — 4 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-11. A secondary CVSS source baseline 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.7%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%The EG Score, 8.8 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.7%
- EPSS %ILE
- 76th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 11, 2026
Last Modified
October 13, 2026
Advisory Details (5)
Auto-updated Oct 11, 2026Patch available. Sources: github_commit, github.
Web page
databasement/composer.json at bcee6f0e62796337aaac26961c41f7eb9578dd76 · David-Crty/databasement · GitHub
https://github.com/David-Crty/databasement/blob/bcee6f0e62796337aaac26961c41f7eb9578dd76/composer.json#L3GitHub commit Patch Available
commit 22258e3eac59 (David-Crty/databasement)
Patch available: David-Crty/databasement v1.8.2 (contains commit 22258e3eac59)
https://github.com/David-Crty/databasement/commit/22258e3eac594e653f9d04a69d93e83923d61499GitHub commit Patch Available
commit 2d2761905594 (David-Crty/databasement)
Patch available: David-Crty/databasement v1.7.6 (contains commit 2d2761905594)
https://github.com/David-Crty/databasement/commit/2d2761905594a2fa2c3d81d48a7c8b6a1784862cWeb page
databasement/app/Services/Backup/Databases/MysqlDatabase.php at bcee6f0e62796337aaac26961c41f7eb9578dd76 · David-Crty/databasement · GitHub
https://github.com/David-Crty/databasement/blob/bcee6f0e62796337aaac26961c41f7eb9578dd76/app/Services/Backup/Databases/MysqlDatabase.php#L22GitHub advisoryMentions a patch (unverified)
Authenticated RCE via the Backup "Database Names" Field · Advisory · David-Crty/databasement · GitHub
https://github.com/David-Crty/databasement/security/advisories/GHSA-hm57-pvxc-4pcmVendor Advisories for CVE-2026-108963(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.7% · 76th percentile
- 2026-10-13 14:26 UTCEG score recompute
- 2026-10-13 14:26 UTCGHSA enrichmentGHSA-7cxh-ppfp-4mq4 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-13 14:10 UTCEG score recompute
- 2026-10-13 14:10 UTCGHSA enrichmentGHSA-7cxh-ppfp-4mq4 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.7% · 76th percentile
- 2026-10-11 20:25 UTCEG score recompute
- 2026-10-11 19:50 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-11 19:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108963?
CVE-2026-108963 is a high-severity vulnerability; its CVE record was published on October 11, 2026. 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…
When was the CVE record for CVE-2026-108963 published?
The CVE record for CVE-2026-108963 was published on October 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-108963 actively exploited?
CVE-2026-108963 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108963?
CVE-2026-108963 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108963?
A fix for CVE-2026-108963 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-108963 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108963
Is Your Infrastructure Affected by CVE-2026-108963?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.