# CVE-2025-70364: Code injection in n/a

> Authenticated administrators can execute arbitrary PHP code on the server, although the vendor claims this is an intended feature.


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 9 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-qcqx-gfxj-4j65

## What is CVE-2025-70364?

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

### Official description

An issue was discovered in Kiamo before 8.4 allowing authenticated administrative attackers to execute arbitrary PHP code on the server. NOTE: the Supplier's position is that this is "a historical and intended administrative feature of the product, accessible only to already authenticated users explicitly granted administrator privileges." However, restrictions on some PHP functions were added in 8.4.

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

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


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

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

## Is CVE-2025-70364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70364 is a high-severity code injection vulnerability in n/a, published on 9 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-2025-70364 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-2025-70364/ (Markdown: https://insights.sbomify.com/CVE-2025-70364/index.md)
```

## Sources

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

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