# CVE-2021-31769: Command injection in n/a

> Unauthenticated attackers can execute arbitrary OS commands via the Task Scheduler due to missing authorization in the file selection 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:** 21 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6h74-32fr-fmfm

## What is CVE-2021-31769?

CVE-2021-31769 is a high-severity command injection vulnerability in n/a, published on 21 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MyQ Server in MyQ X Smart before 8.2 allows remote code execution by unprivileged users because administrative session data can be read in the %PROGRAMFILES%\MyQ\PHP\Sessions directory. The "Select server file" feature is only intended for administrators but actually does not require authorization. An attacker can inject arbitrary OS commands (such as commands to create new .php files) via the Task Scheduler component.

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

## Which versions are affected by CVE-2021-31769?

It affects 1 product.


Products: Myq-Solution Myq Server.

## How do I fix CVE-2021-31769?

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

## Is CVE-2021-31769 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-31769 and fix it if it is affected.

What it is: CVE-2021-31769 is a high-severity command injection vulnerability in n/a, published on 21 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-31769 in the wild and no public exploit code.

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-2021-31769/ (Markdown: https://insights.sbomify.com/CVE-2021-31769/index.md)
```

## Sources

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

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