# CVE-2022-36262: Code injection in n/a

> Attackers can inject arbitrary PHP code via website settings in taocms, leading to remote code execution.

- **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:** 15 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-364p-6jx5-j5jv

## What is CVE-2022-36262?

CVE-2022-36262 is a critical code injection vulnerability in n/a, published on 15 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in taocms 3.0.2. in the website settings that allows arbitrary php code to be injected by modifying config.php.

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

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

It affects 1 product.


Products: Taogogo Taocms.

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

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

## Is CVE-2022-36262 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-33350](https://insights.sbomify.com/CVE-2024-33350/): Path traversal in n/a (critical 9.8)
- [CVE-2022-48006](https://insights.sbomify.com/CVE-2022-48006/): File upload in n/a (critical 9.8)
- [CVE-2022-46998](https://insights.sbomify.com/CVE-2022-46998/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-23880](https://insights.sbomify.com/CVE-2022-23880/): File upload in n/a (critical 9.8)
- [CVE-2022-25505](https://insights.sbomify.com/CVE-2022-25505/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36262 is a critical code injection vulnerability in n/a, published on 15 Aug 2022. 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-2022-36262 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-2022-36262/ (Markdown: https://insights.sbomify.com/CVE-2022-36262/index.md)
```

## Sources

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

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