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

> Unauthenticated attackers can execute arbitrary code via XSS in the DMARC report viewer dashboard using org_name or domain values.

- **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:** 22 Jun 2023
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-672p-gf4j-x5jc

## What is CVE-2023-34796?

CVE-2023-34796 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Jun 2023. 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

Cross site scripting (XSS) vulnerabiliy in dmarcts-report-viewer dashboard versions 1.1 and thru commit 8a1d882b4c481a05e296e9b38a7961e912146a0f, allows unauthenticated attackers to execute arbitrary code via the org_name or domain values.

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

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

It affects 1 product.


Products: Techsneeze Dmarc Report.

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

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

## Is CVE-2023-34796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34796 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34796 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-2023-34796/ (Markdown: https://insights.sbomify.com/CVE-2023-34796/index.md)
```

## Sources

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

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