CVE-2026-34113
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 speech_text.php (line 18) without sanitization: exec(\"php jobs/speech_audio_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 speech_text.php where the 'id' GET parameter is passed directly to a PHP exec() call without any sanitization or validation. An unauthenticated 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 the vulnerable speech_text.php fileSearch the web root directory for speech_text.php using: find /var/www -name 'speech_text.php' 2>/dev/null (Linux) or dir /s speech_text.php (Windows)Affected if The file exists and is web-accessible in the application directory
-
Verify the application is Guardian language-systemCheck the application's source code, footer, or documentation to confirm the product name is 'Guardian' or 'Guardian language-system'Affected if The application is the Guardian language-system product
-
Determine the installed versionCheck for a version file, CHANGELOG, or look for a version constant in the PHP source code: grep -r 'version' /path/to/guardian/ 2>/dev/nullAffected if The installed version is unknown or falls within any version range published by the vendor for this product
-
Test for the vulnerable parameterSend a benign HTTP request to speech_text.php with the 'id' parameter, e.g., GET /speech_text.php?id=test;echo VulnerabilityAffected if The application returns output from the injected command, indicating command execution
-
Check unauthenticated access is possibleConfirm the speech_text.php endpoint does not require authentication by attempting the request without any session or credentialsAffected if The request completes without HTTP 401/403 authentication errors
If speech_text.php is accessible without authentication and the 'id' parameter executes injected shell commands, the environment is affected by this command injection vulnerability.
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 strict input validation and sanitization for the 'id' parameter, preferably using whitelisting of allowed characters. Consider refactoring to avoid exec() calls entirely, or use parameterized approaches that separate command arguments from user input.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34113 — 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-34113 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