# CVE-2026-30643: Code injection in n/a

> Attackers can execute arbitrary code by submitting crafted setup tag values during module uploads in DedeCMS.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-vc3q-w6jg-xcpj

## What is CVE-2026-30643?

CVE-2026-30643 is a critical code injection vulnerability in Dedecms Dedecms, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in DedeCMS 5.7.118 allowing attackers to execute code via crafted setup tag values in a module upload.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Dedecms Dedecms.

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

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

## Is CVE-2026-30643 being exploited?

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

## Other vulnerabilities in Dedecms Dedecms

- [CVE-2026-30694](https://insights.sbomify.com/CVE-2026-30694/): Code injection in n/a (critical 9.8)
- [CVE-2024-35510](https://insights.sbomify.com/CVE-2024-35510/): File upload in n/a (critical 9.8)
- [CVE-2024-35375](https://insights.sbomify.com/CVE-2024-35375/): File upload in n/a (critical 9.8)
- [CVE-2024-29661](https://insights.sbomify.com/CVE-2024-29661/): File upload in n/a (critical 9.8)
- [CVE-2024-29684](https://insights.sbomify.com/CVE-2024-29684/): Cross-site request forgery in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30643 is a critical code injection vulnerability in Dedecms Dedecms, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30643 exists.

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

## Sources

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

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