# CVE-2023-45552: Cross-site scripting in n/a

> An authenticated attacker can execute stored XSS in the admin portal to take over all user accounts.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-rg6q-wc9f-whjv

## What is CVE-2023-45552?

CVE-2023-45552 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In VeridiumID before 3.5.0, a stored cross-site scripting (XSS) vulnerability has been discovered in the admin portal that allows an authenticated attacker to take over all accounts by sending malicious input via the self-service portal.

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

## Which versions are affected by CVE-2023-45552?

It affects 1 product.


Products: Veridiumid Veridiumad.

## How do I fix CVE-2023-45552?

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

## Is CVE-2023-45552 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-44039](https://insights.sbomify.com/CVE-2023-44039/): Auth bypass in n/a (critical 9.1)
- [CVE-2021-42791](https://insights.sbomify.com/CVE-2021-42791/): Missing authorization in n/a (high 7.3)
- [CVE-2023-44038](https://insights.sbomify.com/CVE-2023-44038/): Information disclosure in n/a (medium 6.5)
- [CVE-2023-44040](https://insights.sbomify.com/CVE-2023-44040/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45552 and fix it if it is affected.

What it is: CVE-2023-45552 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45552 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-2023-45552/ (Markdown: https://insights.sbomify.com/CVE-2023-45552/index.md)
```

## Sources

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

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