Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege credentials
-
DeliverySend crafted HTTP GET to designer.php with injected name parameter
-
ExploitTrigger error-based SQL execution in database
-
ExecutionParse extracted data from error responses
-
ImpactExfiltrate database contents iteratively
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The CVE description specifies that an authenticated attacker is required, consistent with the CVSS 4.0 PR:L metric indicating low-level privileges are needed. The vulnerable endpoint is designer.php, which must be publicly reachable over HTTP/HTTPS; if this file is not web-accessible or is restricted by server configuration, exploitation is blocked. The application must return verbose SQL error messages to the HTTP response for error-based extraction to succeed - suppressing database errors (e.g., via PHP display_errors=Off and custom error handling) would prevent data exfiltration via this technique, though blind injection variants may still be possible. CRITICAL DISCREPANCY: The VulnCheck advisory title describes the flaw as 'unauthenticated' while the CVE description states 'authenticated' and PR:L confirms some credentials are required - the actual authentication prerequisite must be independently verified with the vendor before finalizing defensive posture, as it materially changes the attack surface. |
| Impact | The CVSS 4.0 base score of 8.7 with a vector of AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H accurately reflects a severe, remotely exploitable vulnerability with minimal attack complexity. However, EPSS sits at only 0.37% (29th percentile), suggesting low observed exploitation activity in the wild at time of analysis despite the public POC - this low EPSS may reflect the product's limited deployment footprint rather than genuine low attacker interest. The SSVC classification of Automatable:Yes and Technical Impact:Total elevates urgency significantly: a scripted tool could enumerate and extract the entire database without manual effort, making this attractive for opportunistic bulk scanning even against a niche target. The POC hosted on GitHub Gist lowers the bar further by providing ready-made exploit code. The authentication discrepancy between the CVE description (authenticated) and the VulnCheck title (unauthenticated) is the single most critical unresolved data point - if exploitation truly requires no credentials, the effective risk is materially higher than PR:L implies, and even a small operator running this software should treat immediate remediation as urgent regardless of their scale. |
| Exploit ScenarioDerived | An attacker with low-privilege credentials (or, if the VulnCheck title is correct, no credentials at all) sends a crafted HTTP GET request to designer.php with a malicious |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Aug 24, 2026
SQL injection in Guardian Language-System's designer.php (line 124) allows attackers to extract, modify, or destroy the full database contents by manipulating the unsanitized name GET parameter passed directly into a raw SQL query. A public proof-of-concept exploit exists via GitHub Gist, and SSVC analysis classifies the attack as automatable with total technical impact. A notable discrepancy exists between sources: the CVE description and the CVSS 4.0 vector (PR:L) indicate low-privilege authentication is required, while the VulnCheck advisory title labels this 'unauthenticated' - defenders must verify the actual authentication requirement before calibrating response priority.
Earlier versions of this analysis (2)
SQL injection in Guardian language-system's designer.php exposes database contents to authenticated network attackers via the unsanitized name GET parameter passed directly into a raw SQL query at line 124. All versions up to commit e42c395ec4b03fe62973a669c9209a673838b8a4 are affected, with the vulnerable parameter reachable over HTTP without additional configuration. A publicly available proof-of-concept exploit exists (VulnCheck, GitHub gist), and SSVC rates the technical impact as total with the attack automatable - though automation is constrained by the authentication prerequisite confirmed by the CVSS PR:L metric.
SQL injection in Guardian Language-System's designer.php exposes the entire backend database to attackers who supply a crafted 'name' GET parameter, which is concatenated directly into a SELECT query without sanitization (CWE-89). VulnCheck reports this as remotely reachable and publicly available exploit code exists, though no public exploit is confirmed as actively used in the wild (not in CISA KEV). Note a source conflict: the CVE description labels the attacker 'authenticated' while the VulnCheck advisory and CVSS 4.0 vector (PR:N) describe it as unauthenticated.
RemediationAI
Upstream fix available (PR/commit); released patched version not independently confirmed - operators should update to any commit after e42c395ec4b03fe62973a669c9209a673838b8a4 from the Guardian Language-System repository and verify the fix is applied to designer.php line 124. The correct long-term fix is to replace the raw string concatenation with a parameterized prepared statement using PHP's PDO or MySQLi extension. As an immediate compensating control, restrict access to designer.php via web server configuration (e.g., Apache .htaccess or nginx location block) to trusted IP ranges only - this eliminates network exposure but may break legitimate designer functionality for remote users. Alternatively, place an authenticated reverse proxy or WAF with SQL injection signatures in front of the application; WAF rules can block obvious error-based payloads but should not be treated as a permanent substitute for code-level remediation. Consult the VulnCheck advisory at https://www.vulncheck.com/advisories/guardian-language-system-unauthenticated-sql-injection-via-name-parameter-in-designer-php and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-34104 for any updated vendor guidance.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Guardian Language-System is a PHP-based application for managing multilingual content, identified by CPE cpe:2.3:a:guardian:language-system:*:*:*:*:*:*:*:*. The vulnerability is rooted in CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), the classic SQL injection root cause. At designer.php line 124, the $_GET['name'] superglobal is concatenated directly into a SQL string - SELECT * FROM complex WHERE name='".$_GET['name']."' - with no parameterization, prepared statements, or escaping. The error-based exploitation technique relies on the application returning database error messages to the HTTP response, allowing an attacker to exfiltrate schema and data column-by-column by crafting inputs that trigger structured SQL errors. PHP applications using raw string concatenation for database queries are particularly susceptible because there is no framework-level protection layer enforcing parameterized queries.
Know when Guardian gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Network-reachable endpoint, no complexity, low-privilege auth per description and PR:L in provided 4.0 vector; scope unchanged as impact stays within the application's database.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
Guardian language-system passes the name GET parameter directly into an unsanitized SQL query in designer.php (line 124): SELECT * FROM complex WHERE name='\".$_GET['name'].\"'. An authenticated attacker can perform error-based SQL injection to extract database contents.
Executive ViewAI
Guardian Language-System users face immediate risk of complete data compromise-attackers with low-privilege access can steal, modify, or destroy the entire database using publicly available exploit code. Every instance running this product is vulnerable to automated attacks until remediated. This requires urgent action to protect sensitive information and maintain data integrity across all Guardian deployments.
No vendor-released patch identified at time of analysis. Mitigations: restrict network access to designer.php via firewall or IP allowlist; deploy WAF rules to block SQL injection payloads targeting the name parameter; implement least-privilege database credentials for the Guardian application account; enable SQL query logging and alerting for suspicious patterns; maintain automated, immutable backups with 30+ day retention to enable recovery from database compromise.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
OS command injection in Guardian language-system lets unauthenticated remote attackers run arbitrary shell commands by i
Remote code execution in Guardian language-system allows unauthenticated attackers to run arbitrary OS commands by injec
Unauthenticated SQL injection in Guardian Language System lets remote attackers manipulate the backend database by injec
Error-based SQL injection in Guardian Language-System allows a network-accessible authenticated attacker to extract the
Error-based SQL injection in Guardian language-system's subtitles.php exposes full database contents to low-privileged a
Error-based SQL injection in Guardian Language-System exposes the full database to low-privileged authenticated attacker
Error-based SQL injection in Guardian language-system's text_file.php exposes the full database to extraction via a triv
SQL injection in Guardian language-system's media.php endpoint allows low-privilege authenticated attackers to extract t
Nozomi Networks OS before 19.0.4 allows /#/network?tab=network_node_list.html CSV Injection. Rated high severity (CVSS 7
Nozomi Guardian before 19.0.4 allows attackers to achieve stored XSS (in the web front end) by leveraging the ability to
A SQL Injection vulnerability in Nozomi Networks Guardian and CMC, due to improper input validation in certain fields us
Reflected cross-site scripting in Guardian Language-System's media.php allows authenticated attackers to inject arbitrar
EUVD-2026-41061
GHSA-8333-3mcf-q3cc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB