CVE-2026-34108
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGuardian language-system passes the id GET parameter directly into a PHP exec() call in text.php (line 15) without sanitization: exec(\"php jobs/text.php \".$login_session.\" \".$_GET['id'].\" ...\"). No authentication is required. An unauthenticated remote attacker can append shell metacharacters to execute arbitrary OS commands on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Guardian language-system contains a critical command injection vulnerability in text.php where the 'id' GET parameter is passed directly to a PHP exec() call without any sanitization or escaping. An unauthenticated remote attacker can inject shell metacharacters via the id parameter to execute arbitrary operating system commands on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate text.php in the Guardian installationSearch the web root or application directory for the file text.php. Common paths may include /text.php, /lang/text.php, or /scripts/text.php.Affected if The file text.php exists in the Guardian language-system installation directory.
-
Check the Guardian versionExamine any version file, composer.json, or header comments in text.php for a version identifier. Compare against any official version releases of Guardian.Affected if The installed version matches or precedes the version range containing the fix for CVE-2026-34108.
-
Examine line 15 of text.php for exec() callOpen text.php and inspect line 15. Look for a PHP exec() function that receives the id parameter from $_GET['id'] without sanitization.Affected if Line 15 contains an exec() call using the id GET parameter directly without input validation.
-
Verify the vulnerable parameter handlingSearch the text.php file for the pattern where $_GET['id'] is passed to exec() or similar shell execution functions (shell_exec, system, passthru) without sanitization functions like escapeshellarg or preg_replace.Affected if The id parameter is passed to a shell execution function without being processed through escapeshellarg() or equivalent input sanitization.
-
Confirm network accessibility of the affected endpointAttempt to access text.php?id=test via HTTP request to determine if the endpoint is exposed and reachable.Affected if The text.php file is accessible over the network, allowing an attacker to send a crafted id parameter.
If text.php exists with the vulnerable exec() pattern on line 15 using unsanitized id input and is network-accessible, the environment is affected by CVE-2026-34108.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement immediate input validation and escaping on all user-supplied parameters before passing to exec(), preferably using escapeshellarg() or removing exec() entirely in favor of safer alternatives; consider deploying a WAF rule as a temporary compensating control.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34108 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data