# CVE-2025-30091: Code injection in MoxieManager PHP

> Unauthenticated attackers can inject and execute arbitrary code via the installer command in Tiny MoxieManager PHP.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-fp8m-c995-8jh3

## What is CVE-2025-30091?

CVE-2025-30091 is a critical code injection vulnerability in Tiny MoxieManager PHP, published on 25 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Tiny MoxieManager PHP before 4.0.0, remote code execution can occur in the installer command. This vulnerability allows unauthenticated attackers to inject and execute arbitrary code. Attacker-controlled data to InstallCommand can be inserted into config.php, and InstallCommand is available after an installation has completed.

Weakness: CWE-96 (Improper Neutralization of Directives in Statically Saved Code)

## Which versions are affected by CVE-2025-30091?


## How do I fix CVE-2025-30091?

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

## Is CVE-2025-30091 being exploited?

There is no known exploitation of CVE-2025-30091 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30091 and fix it if it is affected.

What it is: CVE-2025-30091 is a critical code injection vulnerability in Tiny MoxieManager PHP, published on 25 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30091 in the wild and no public exploit code.

Affected product: Tiny MoxieManager PHP. 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-2025-30091/ (Markdown: https://insights.sbomify.com/CVE-2025-30091/index.md)
```

## Sources

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

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