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

> Attackers can inject malicious HTML into the Account page Name field, potentially executing scripts or stealing user sessions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-cw5r-qw3x-wgpf

## What is CVE-2022-40434?

CVE-2022-40434 is a critical cross-site scripting vulnerability in n/a, published on 19 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Softr v2.0 was discovered to be vulnerable to HTML injection via the Name field of the Account page.

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

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

It affects 1 product.


Products: Softr Softr.

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

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

## Is CVE-2022-40434 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40434 exists.

## Other vulnerabilities in n/a

- [CVE-2022-32407](https://insights.sbomify.com/CVE-2022-32407/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-48085](https://insights.sbomify.com/CVE-2022-48085/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40434 is a critical cross-site scripting vulnerability in n/a, published on 19 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40434 exists.

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-40434/ (Markdown: https://insights.sbomify.com/CVE-2022-40434/index.md)
```

## Sources

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

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