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

> Remote code execution in Hoosk CMS installer allows attackers to execute arbitrary code if the installation script is accessible.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9q46-8mr3-8pxq

## What is CVE-2020-26041?

CVE-2020-26041 is a critical code injection vulnerability in n/a, published on 29 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Hoosk CmS v1.8.0. There is an Remote Code Execution vulnerability in install/index.php

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

It affects 1 product.


Products: Hoosk Hoosk.

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

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

## Is CVE-2020-26041 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43234](https://insights.sbomify.com/CVE-2022-43234/): File upload in n/a (critical 9.8)
- [CVE-2020-26042](https://insights.sbomify.com/CVE-2020-26042/): SQL injection in n/a (critical 9.8)
- [CVE-2018-16771](https://insights.sbomify.com/CVE-2018-16771/): Code injection in n/a (critical 9.8)
- [CVE-2018-7590](https://insights.sbomify.com/CVE-2018-7590/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-51055](https://insights.sbomify.com/CVE-2024-51055/): Cross-site scripting in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26041 is a critical code injection vulnerability in n/a, published on 29 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26041 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-26041/ (Markdown: https://insights.sbomify.com/CVE-2020-26041/index.md)
```

## Sources

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

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