# CVE-2026-34096: Guardian Language-System XSS via name Parameter in designer.php

> An authenticated attacker can execute arbitrary scripts in a victim's browser via the name parameter in designer.php.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 1 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-ggfh-fv42-r856

## What is CVE-2026-34096?

CVE-2026-34096 is a medium-severity cross-site scripting vulnerability in guardian language-system, published on 1 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Guardian language-system fails to sanitize the name GET parameter before outputting it into an HTML input value attribute in designer.php (line 57). An authenticated attacker can craft a URL containing script tags that execute in the victim's browser session.

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

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


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

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

## Is CVE-2026-34096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34096 is a medium-severity cross-site scripting vulnerability in guardian language-system, published on 1 Jul 2026. Any signed-in user can exploit it over the network, 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-2026-34096 exists.

Affected product: guardian language-system. 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-34096/ (Markdown: https://insights.sbomify.com/CVE-2026-34096/index.md)
```

## Sources

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

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