# CVE-2021-43440: Cross-site scripting in n/a

> Remote attackers can execute arbitrary code via stored XSS in the signup form's Name and Phone fields of the iOrder web application.

- **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:** 20 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6hp7-c3wr-r2xv

## What is CVE-2021-43440?

CVE-2021-43440 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Dec 2021. 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

Multiple Stored XSS Vulnerabilities in the Source Code of iOrder 1.0 allow remote attackers to execute arbitrary code via signup form in the Name and Phone number field.

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

## Which versions are affected by CVE-2021-43440?

It affects 1 product.


Products: Iorder Project Iorder.

## How do I fix CVE-2021-43440?

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

## Is CVE-2021-43440 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43441](https://insights.sbomify.com/CVE-2021-43441/): Cross-site scripting in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43440 and fix it if it is affected.

What it is: CVE-2021-43440 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Dec 2021. 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-2021-43440 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-2021-43440/ (Markdown: https://insights.sbomify.com/CVE-2021-43440/index.md)
```

## Sources

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

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