# CVE-2024-22220: Cross-site scripting in n/a

> Unauthenticated attackers can inject scripts via Form Builder or Preview to hijack admin sessions in Terminalfour and Formbank.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 21 Feb 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-mmq5-phxp-hrxq

## What is CVE-2024-22220?

CVE-2024-22220 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Terminalfour 7.4 through 7.4.0004 QP3 and 8 through 8.3.19, and Formbank through 2.1.10-FINAL. Unauthenticated Stored Cross-Site Scripting can occur, with resultant Admin Session Hijacking. The attack vectors are Form Builder and Form Preview.

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

## Which versions are affected by CVE-2024-22220?

It affects 2 products.


Products: Terminalfour Formbank, Terminalfour Terminalfour.

## How do I fix CVE-2024-22220?

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

## Is CVE-2024-22220 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22220 and fix it if it is affected.

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

## Sources

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

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