CVE-2026-34096
Deferred Deferred - Pending Action

Stored XSS in Guardian Language-System Designer

Vulnerability report for CVE-2026-34096, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-01

Last updated on: 2026-07-14

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-01
Last Modified
2026-07-14
Generated
2026-07-21
AI Q&A
2026-07-01
EPSS Evaluated
2026-07-20
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
guardian language-system to commit_e42c395 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Cross-Site Scripting (XSS) issue in the Guardian language-system. It occurs because the system does not properly sanitize the 'name' GET parameter before inserting it into an HTML input value attribute in the file designer.php at line 57.

An authenticated attacker can exploit this by crafting a URL containing malicious script tags. When a victim opens this URL, the script executes in their browser session, potentially leading to unauthorized actions or data exposure.

Detection Guidance

This vulnerability can be detected by checking for the presence of the vulnerable parameter in the designer.php file and testing if the name GET parameter is properly sanitized.

One way to detect the vulnerability is to send a crafted HTTP request to the designer.php page with a script tag in the name parameter and observe if the script executes or is reflected unsanitized in the HTML response.

Example command using curl to test the vulnerability:

  • curl -i "http://[target]/designer.php?name=<script>alert('XSS')</script>"

If the response contains the script tag unescaped inside an HTML input value attribute, the system is vulnerable.

Additionally, monitoring web server logs for suspicious URLs containing script tags in the name parameter can help detect exploitation attempts.

Impact Analysis

The vulnerability allows an authenticated attacker to execute arbitrary scripts in the victim's browser session. This can lead to impacts such as theft of session cookies, defacement of web content, or performing actions on behalf of the victim without their consent.

Since the attacker must be authenticated, the risk is somewhat limited, but it still poses a medium severity threat with a CVSS score of 4.8.

Compliance Impact

The provided information does not specify how this vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.

Mitigation Strategies

To mitigate this vulnerability, ensure that the name GET parameter in designer.php is properly sanitized before being output into HTML. This prevents execution of malicious script tags in the victim's browser session.

Additionally, restrict access to authenticated users only and consider applying patches or updates that address this issue in the Guardian language-system.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-34096. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart