# CVE-2021-27811: Code injection in n/a

> Attackers can execute arbitrary PHP code via the Upgrade function in QibosoftX1, potentially compromising the web server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2p4f-q7g6-g44m

## What is CVE-2021-27811?

CVE-2021-27811 is a high-severity code injection vulnerability in n/a, published on 21 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A code injection vulnerability has been discovered in the Upgrade function of QibosoftX1 v1.0. An attacker is able execute arbitrary PHP code via exploitation of client_upgrade_edition.php and Upgrade.php.

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

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

It affects 1 product.


Products: Qibosoft Qibosoft.

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

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

## Is CVE-2021-27811 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17613](https://insights.sbomify.com/CVE-2019-17613/): Code injection in n/a (critical 9.8)
- [CVE-2020-20944](https://insights.sbomify.com/CVE-2020-20944/): Path traversal in n/a (critical 9.1)
- [CVE-2020-20945](https://insights.sbomify.com/CVE-2020-20945/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-18201](https://insights.sbomify.com/CVE-2018-18201/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-5725](https://insights.sbomify.com/CVE-2019-5725/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-27811 is a high-severity code injection vulnerability in n/a, published on 21 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27811 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-27811/ (Markdown: https://insights.sbomify.com/CVE-2021-27811/index.md)
```

## Sources

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

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