# CVE-2026-19353: DedeCMS Installation Wizard index.php _4_Setup file inclusion

> Remote attackers can exploit file inclusion in the DedeCMS installation wizard to potentially execute code or read sensitive files.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 9 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-qg5x-jc32-6g34

## What is CVE-2026-19353?

CVE-2026-19353 is a low-severity path traversal vulnerability in DedeCMS, published on 9 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in DedeCMS up to 5.7.118 UTF8SP2. The affected element is the function _4_Setup of the file install/index.php of the component Installation Wizard. Such manipulation leads to file inclusion. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is described as difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-19353 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19353 is a low-severity path traversal vulnerability in DedeCMS, published on 9 Aug 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-19353 exists.

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

## Sources

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

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