# CVE-2020-26124: Code injection in n/a

> Authenticated attackers can inject PHP code via the sortfield parameter to execute arbitrary commands as root on openmediavault systems.

- **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:** 2 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f68r-v9vp-fxgw

## What is CVE-2020-26124?

CVE-2020-26124 is a high-severity code injection vulnerability in n/a, published on 2 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

openmediavault before 4.1.36 and 5.x before 5.5.12 allows authenticated PHP code injection attacks, via the sortfield POST parameter of rpc.php, because json_encode_safe is not used in config/databasebackend.inc. Successful exploitation allows arbitrary command execution on the underlying operating system as root.

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

## Which versions are affected by CVE-2020-26124?

It affects 1 product.


Products: Openmediavault Openmediavault.

## How do I fix CVE-2020-26124?

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

## Is CVE-2020-26124 being exploited?

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

Public exploit code:

- OpenMediaVault rpc.php Authenticated PHP Code Injection (metasploit)

## Other vulnerabilities in n/a

- [CVE-2013-3632](https://insights.sbomify.com/CVE-2013-3632/): Command injection in n/a (high 8.8)
- [CVE-2025-50674](https://insights.sbomify.com/CVE-2025-50674/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-1000065](https://insights.sbomify.com/CVE-2017-1000065/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26124 and fix it if it is affected.

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

## Sources

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

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