CVE-2026-34098
Deferred Deferred - Pending Action

Guardian Language-System Stored XSS via Unsanitized id Parameter

Vulnerability report for CVE-2026-34098, 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 id GET parameter before inserting it into HTML source and form action attributes in media.php (lines 119, 129). An authenticated attacker can craft a URL that injects script tags executing 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 guardian_language_system to e42c395 (inc)

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 occurs because the Guardian language-system does not properly sanitize the 'id' parameter received via a GET request before inserting it into the HTML source and form action attributes in the media.php file. As a result, an authenticated attacker can craft a malicious URL that injects script tags, which then execute in the victim's browser session.

Detection Guidance

This vulnerability can be detected by identifying attempts to exploit the unsanitized id GET parameter in media.php. Specifically, monitoring for URLs containing suspicious script tags or JavaScript code injected into the id parameter is key.

You can use web server logs or network traffic analysis tools to search for requests to media.php with the id parameter containing script tags or other suspicious payloads.

  • Use grep or similar tools on web server logs to find suspicious requests, for example: grep -i "media.php?id=<script" access.log
  • Use a web application scanner or proxy tool (like OWASP ZAP or Burp Suite) to test the id parameter for XSS injection by sending crafted URLs.
Impact Analysis

The impact of this vulnerability is that an attacker with authentication can execute arbitrary scripts in the context of a victim's browser session. This can lead to information disclosure, session hijacking, or other malicious actions that compromise the confidentiality and integrity of the user's data.

Mitigation Strategies

Immediate mitigation involves sanitizing and validating the id GET parameter before it is inserted into HTML source and form action attributes.

Ensure that the application properly neutralizes any input to prevent script injection, such as encoding special characters or using secure frameworks that handle output encoding.

Additionally, restrict access to authenticated users only, as the vulnerability requires authentication, and consider applying patches or updates if available.

Chat Assistant

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

EPSS Chart