# CVE-2022-42458: Auth bypass in bingo!CMS

> Remote attackers can bypass authentication to upload arbitrary files, leading to script execution or file modification in bingo!CMS.

- **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:** 7 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-c6jj-hc2x-m9jc

## What is CVE-2022-42458?

CVE-2022-42458 is a critical authentication bypass vulnerability in Shift Tech Inc. bingo!CMS, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass using an alternate path or channel vulnerability in bingo!CMS version1.7.4.1 and earlier allows a remote unauthenticated attacker to upload an arbitrary file. As a result, an arbitrary script may be executed and/or a file may be altered.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Shift-Tech Bingo\!cms.

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

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

## Is CVE-2022-42458 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42458 is a critical authentication bypass vulnerability in Shift Tech Inc. bingo!CMS, published on 7 Dec 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-42458 in the wild and no public exploit code.

Affected product: Shift Tech Inc. bingo!CMS. 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-42458/ (Markdown: https://insights.sbomify.com/CVE-2022-42458/index.md)
```

## Sources

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

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