# CVE-2019-20460: Cross-site request forgery in n/a

> Attackers can exploit missing CSRF protections on Epson printers to force unauthorized print jobs via crafted POST requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Nov 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-prv6-6759-h8fv

## What is CVE-2019-20460?

CVE-2019-20460 is a high-severity vulnerability in n/a, published on 7 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered on Epson Expression Home XP255 20.08.FM10I8 devices. POST requests don't require (anti-)CSRF tokens or other mechanisms for validating that the request is from a legitimate source. In addition, CSRF attacks can be used to send text directly to the RAW printer interface. For example, an attack could deliver a worrisome printout to an end user.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-20460?


## How do I fix CVE-2019-20460?

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

## Is CVE-2019-20460 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20460 and fix it if it is affected.

What it is: CVE-2019-20460 is a high-severity vulnerability in n/a, published on 7 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20460 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-2019-20460/ (Markdown: https://insights.sbomify.com/CVE-2019-20460/index.md)
```

## Sources

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

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