# CVE-2026-30461: Command injection in n/a

> Authenticated attackers can execute arbitrary code in FuelCMS via the add_git_submodule function in the installer controller.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **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:** 15 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-q6p9-89h2-c9h9

## What is CVE-2026-30461?

CVE-2026-30461 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Daylight Studio FuelCMS v1.5.2 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the /controllers/Installer.php and the function add_git_submodule.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Thedaylightstudio Fuel Cms.

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

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

## Is CVE-2026-30461 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-17463](https://insights.sbomify.com/CVE-2020-17463/): Fuel CMS SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-22151](https://insights.sbomify.com/CVE-2020-22151/): File upload in n/a (critical 9.8)
- [CVE-2020-22153](https://insights.sbomify.com/CVE-2020-22153/): File upload in n/a (critical 9.8)
- [CVE-2021-38727](https://insights.sbomify.com/CVE-2021-38727/): SQL injection in n/a (critical 9.8)
- [CVE-2020-24791](https://insights.sbomify.com/CVE-2020-24791/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30461 is a high-severity command injection vulnerability in n/a, published on 15 Apr 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-30461 exists.

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

## Sources

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

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