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

> Attackers can inject malicious scripts via registration fields, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-qrh5-67c8-cw6q

## What is CVE-2022-43097?

CVE-2022-43097 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Phpgurukul User Registration & User Management System v3.0 was discovered to contain multiple stored cross-site scripting (XSS) vulnerabilities via the firstname and lastname parameters of the registration form & login pages.

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

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

It affects 1 product.


Products: User Registration \& User Management System Project User Registration \& User Management System.

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

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

## Is CVE-2022-43097 being exploited?

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

Public exploit code:

- All details about CVE-2022-43097 (github_poc): https://github.com/nibin-m/CVE-2022-43097

## Fix prompt for AI coding agents

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

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

## Sources

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

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