# CVE-2013-6033: Cross-site scripting in n/a

> Remote authenticated users can inject arbitrary web script or HTML via SNMP or Embedded Web Server fields in Lexmark printers.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hmm8-xpc3-h6x5

## What is CVE-2013-6033?

CVE-2013-6033 is a low-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities on Lexmark W840 through LS.HA.P252, T64x before LS.ST.P344, C935dn through LC.JO.P091, C920 through LS.TA.P152, C53x through LS.SW.P069, C52x through LS.FA.P150, E450 through LM.SZ.P124, E350 through LE.PH.P129, and E250 through LE.PM.P126 printers allow remote authenticated users to inject arbitrary web script or HTML by using (1) SNMP or (2) the Embedded Web Server (EWS) to set the (a) Contact or (b) Location field.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2013-6033?

It affects 9 products.


Products: Lexmark C52x, Lexmark C53x, Lexmark C920, Lexmark C935dn, Lexmark E250, Lexmark E350, Lexmark E450, Lexmark T64x, Lexmark W840.

## How do I fix CVE-2013-6033?

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

## Is CVE-2013-6033 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6033 and fix it if it is affected.

What it is: CVE-2013-6033 is a low-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6033 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-2013-6033/ (Markdown: https://insights.sbomify.com/CVE-2013-6033/index.md)
```

## Sources

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

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