# CVE-2026-44956: Cross-site scripting in Adserver

> Low-privileged users can inject malicious scripts via their Full Name, which execute when admins view system-generated emails in the user log.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-55h8-q58m-2332

## What is CVE-2026-44956?

CVE-2026-44956 is a cross-site scripting vulnerability in Revive Adserver, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Low‑privileged users could use their Full Name as a vector for a stored XSS attack. The name is included in system‑generated emails, whose content is stored in the details field of the userlog table. An admin user viewing the email content through userlog-details.php would have any malicious JavaScript payload executed due to missing output sanitisation. Proper escaping has been added to the userlog details output.

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

## Which versions are affected by CVE-2026-44956?


## How do I fix CVE-2026-44956?

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

## Is CVE-2026-44956 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44956 and fix it if it is affected.

What it is: CVE-2026-44956 is a cross-site scripting vulnerability in Revive Adserver, published on 23 Jun 2026. 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-2026-44956 in the wild and no public exploit code.

Affected product: Revive Adserver. 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-2026-44956/ (Markdown: https://insights.sbomify.com/CVE-2026-44956/index.md)
```

## Sources

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

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