# CVE-2022-40912: Cross-site scripting in n/a

> Cross-site scripting in ETAP Safety Manager allows attackers to execute arbitrary HTML/JS code in user browsers via the action parameter.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-m743-qg9w-346q

## What is CVE-2022-40912?

CVE-2022-40912 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ETAP Lighting International NV ETAP Safety Manager 1.0.0.32 is vulnerable to Cross Site Scripting (XSS). Input passed to the GET parameter 'action' is not properly sanitized before being returned to the user. This can be exploited to execute arbitrary HTML/JS code in a user's browser session in context of an affected site.

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

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

It affects 1 product.


Products: Etaplighting Etap Safety Manager.

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

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

## Is CVE-2022-40912 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-50802](https://insights.sbomify.com/CVE-2022-50802/): ETAP Safety Manager 1.0.0.32 Unauthenticated Reflected Cross-Site Scripting via Action Parameter (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40912 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-40912 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-40912/ (Markdown: https://insights.sbomify.com/CVE-2022-40912/index.md)
```

## Sources

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

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