# CVE-2022-42908: Cross-site scripting in Wepa Print Away

> Attackers can inject malicious scripts via unsanitized filenames in WEPA Print Away, leading to persistent XSS attacks against users.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-fgm8-jrv2-6fww

## What is CVE-2022-42908?

CVE-2022-42908 is a medium-severity cross-site scripting vulnerability in Wepa Print Away, published on 3 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

WEPA Print Away is vulnerable to a stored XSS. It does not properly sanitize uploaded filenames, allowing an attacker to deceive a user into uploading a document with a malicious filename, which will be included in subsequent HTTP responses, allowing a stored XSS to occur. This attack is persistent across victim sessions.

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

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

It affects 1 product.


Products: Wepanow Print Away.

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

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

## Is CVE-2022-42908 being exploited?

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

## Other vulnerabilities in Wepa Print Away

- [CVE-2022-42909](https://insights.sbomify.com/CVE-2022-42909/): Missing authorization in Wepa Print Away (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42908 is a medium-severity cross-site scripting vulnerability in Wepa Print Away, published on 3 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-42908 in the wild and no public exploit code.

Affected product: Wepa Print Away. 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-42908/ (Markdown: https://insights.sbomify.com/CVE-2022-42908/index.md)
```

## Sources

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

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