# CVE-2022-36133: Auth bypass in n/a

> Attackers can bypass authentication on Epson TM-C3500 and TM-C7500 label printers via the WebConfig interface.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 25 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-c4w8-pfrf-hc8p

## What is CVE-2022-36133?

CVE-2022-36133 is a critical authentication bypass vulnerability in n/a, published on 25 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WebConfig functionality of Epson TM-C3500 and TM-C7500 devices with firmware version WAM31500 allows authentication bypass.

Weakness: CWE-287 (Improper Authentication)

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

It affects 9 products.


Products: Epson Tm-C3500 Firmware, Epson Tm-C3510 Firmware, Epson Tm-C3520 Firmware, Epson Tm-C7500 Firmware, Epson Tm-C7500g Firmware, Epson Tm-C7510 Firmware, Epson Tm-C7510g Firmware, Epson Tm-C7520 Firmware, Epson Tm-C7520g Firmware.

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

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

## Is CVE-2022-36133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36133 is a critical authentication bypass vulnerability in n/a, published on 25 Nov 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-36133 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-36133/ (Markdown: https://insights.sbomify.com/CVE-2022-36133/index.md)
```

## Sources

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

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