# CVE-2023-50733: A Server-Side Request Forgery (SSRF) vulnerability exists in newer Lexmark devices.

> Attackers can exploit SSRF in Lexmark printer web services to access internal resources or bypass security controls.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2025
- **Updated:** 22 Jan 2025
- **Also known as:** GHSA-pvxw-p6wf-89hg

## What is CVE-2023-50733?

CVE-2023-50733 is a high-severity server-side request forgery vulnerability in Lexmark various, published on 21 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability has been identified in the Web Services feature of newer
Lexmark devices.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-50733?


## How do I fix CVE-2023-50733?

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

## Is CVE-2023-50733 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50733 and fix it if it is affected.

What it is: CVE-2023-50733 is a high-severity server-side request forgery vulnerability in Lexmark various, published on 21 Jan 2025. 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-2023-50733 in the wild and no public exploit code.

Affected product: Lexmark various. 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-2023-50733/ (Markdown: https://insights.sbomify.com/CVE-2023-50733/index.md)
```

## Sources

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

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