# CVE-2020-20945: Cross-site request forgery in n/a

> Attackers can exploit CSRF to arbitrarily add administrator accounts in Qibosoft, leading to privilege escalation and account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-979v-h9jj-r442

## What is CVE-2020-20945?

CVE-2020-20945 is a high-severity vulnerability in n/a, published on 27 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) in /admin/index.php?lfj=member&action=editmember of Qibosoft v7 allows attackers to arbitrarily add administrator accounts.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Qibosoft Qibosoft.

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

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

## Is CVE-2020-20945 being exploited?

There is no known exploitation of CVE-2020-20945 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-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)
- [CVE-2021-27811](https://insights.sbomify.com/CVE-2021-27811/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-20945 is a high-severity vulnerability in n/a, published on 27 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-20945 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-2020-20945/ (Markdown: https://insights.sbomify.com/CVE-2020-20945/index.md)
```

## Sources

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

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