# CVE-2019-11409: Command injection in n/a

> Authenticated non-admin users can execute arbitrary commands on the host via the Operator Panel module, potentially leading to remote code execution.

- **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:** 17 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gfg4-38v6-p8x8

## What is CVE-2019-11409?

CVE-2019-11409 is a high-severity command injection vulnerability in Fusionpbx Fusionpbx, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

app/operator_panel/exec.php in the Operator Panel module in FusionPBX 4.4.3 suffers from a command injection vulnerability due to a lack of input validation that allows authenticated non-administrative attackers to execute commands on the host. This can further lead to remote code execution when combined with an XSS vulnerability also present in the FusionPBX Operator Panel module.

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

## Which versions are affected by CVE-2019-11409?

It affects 1 product.


Products: Fusionpbx Fusionpbx.

## How do I fix CVE-2019-11409?

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

## Is CVE-2019-11409 being exploited?

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

Public exploit code:

- FusionPBX Operator Panel exec.php Command Execution (metasploit)
- FusionPBX - Operator Panel exec.php Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Fusionpbx Fusionpbx

- [CVE-2022-35153](https://insights.sbomify.com/CVE-2022-35153/): Command injection in n/a (critical 9.8)
- [CVE-2022-28055](https://insights.sbomify.com/CVE-2022-28055/): Command injection in n/a (critical 9.8)
- [CVE-2021-43404](https://insights.sbomify.com/CVE-2021-43404/): Path traversal in n/a (high 8.8)
- [CVE-2021-43405](https://insights.sbomify.com/CVE-2021-43405/): Command injection in n/a (high 8.8)
- [CVE-2021-43406](https://insights.sbomify.com/CVE-2021-43406/): Other in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11409 and fix it if it is affected.

What it is: CVE-2019-11409 is a high-severity command injection vulnerability in Fusionpbx Fusionpbx, published on 17 Jun 2019. 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-2019-11409 exists.

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

## Sources

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

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