# CVE-2022-26607: File upload in n/a

> Attackers can execute arbitrary code on baigo CMS by uploading a malicious PHP file, requiring immediate patching or upgrade.

- **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:** 6 Apr 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-xc7v-jvj9-p5fm

## What is CVE-2022-26607?

CVE-2022-26607 is a high-severity vulnerability in n/a, published on 6 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote code execution (RCE) vulnerability in baigo CMS v3.0-alpha-2 was discovered to allow attackers to execute arbitrary code via uploading a crafted PHP file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Baigo Baigo Cms.

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

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

## Is CVE-2022-26607 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9227](https://insights.sbomify.com/CVE-2019-9227/): Code injection in n/a (critical 9.8)
- [CVE-2018-16458](https://insights.sbomify.com/CVE-2018-16458/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2020-20584](https://insights.sbomify.com/CVE-2020-20584/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-9226](https://insights.sbomify.com/CVE-2019-9226/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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