# CVE-2026-72551: Apioo Fusio - Remote Code Execution

> Authenticated developers can execute arbitrary OS commands on the server by bypassing the PHP sandbox allow-list, leading to full system compromise.

- **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:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-j2qp-grc7-qcqj

## What is CVE-2026-72551?

CVE-2026-72551 is a high-severity command injection vulnerability in Apioo Fusio, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A remote code execution vulnerability in Apioo Fusio 8.8.3 allows authenticated users with the Developer role to execute arbitrary OS commands by exploiting a PHP-Sandbox allow-list bypass. The sandbox allow-list permits functions that transitively invoke system(), enabling a developer to escape the sandbox and gain OS command execution on the server. An attacker with a Developer-role account can achieve full server compromise.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-72551 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72551 is a high-severity command injection vulnerability in Apioo Fusio, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72551 in the wild and no public exploit code.

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

## Sources

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

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