# CVE-2022-50909: Algo 8028 Control Panel - Remote Code Execution (RCE) (Authenticated)

> Authenticated attackers can execute arbitrary commands with root privileges via the fm-data.lua endpoint in the Algo 8028 Control Panel.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-qmvp-687p-x9fw

## What is CVE-2022-50909?

CVE-2022-50909 is a high-severity command injection vulnerability in Algo 8028, published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Algo 8028 Control Panel version 3.3.3 contains a command injection vulnerability in the fm-data.lua endpoint that allows authenticated attackers to execute arbitrary commands. Attackers can exploit the insecure 'source' parameter by injecting commands that are executed with root privileges, enabling remote code execution through a crafted POST request.

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

## Which versions are affected by CVE-2022-50909?


## How do I fix CVE-2022-50909?

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

## Is CVE-2022-50909 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50909 and fix it if it is affected.

What it is: CVE-2022-50909 is a high-severity command injection vulnerability in Algo 8028, published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50909 exists.

Affected product: Algo 8028. 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-2022-50909/ (Markdown: https://insights.sbomify.com/CVE-2022-50909/index.md)
```

## Sources

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

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