CVE-2026-34112
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 speechmac.php (line 18) without sanitization: exec(\"php jobs/speech_audio_mac.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 confidenceA critical OS command injection vulnerability exists in Guardian language-system's speechmac.php where the 'id' GET parameter is passed directly into a PHP exec() call without any sanitization or input validation. An unauthenticated attacker can inject shell metacharacters 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 speechmac.php fileSearch the webroot for the file speechmac.php using: find /var/www -name 'speechmac.php' 2>/dev/null (Linux) or dir /s C:\speechmac.php (Windows)Affected if The file exists in the web application directory structure
-
Inspect exec() usage with id parameterOpen speechmac.php and examine lines containing exec() - look for calls that use $_GET['id'] without sanitization functions like escapeshellarg() or escapeshellcmd()Affected if The code shows exec() receiving $_GET['id'] directly without input validation
-
Verify remote accessibilityConfirm the file is web-accessible by checking if it responds to HTTP requests, or by examining web server configuration for the pathAffected if The file is reachable via HTTP/HTTPS without authentication
-
Confirm application is Guardian language-systemCheck the containing application name/version by examining headers, documentation files (README, composer.json, package.json), or application-specific config filesAffected if The application is identified as the Guardian language-system
-
Check for vulnerable parameter handlingReview the full speechmac.php to ensure no input validation exists before the exec() call - look for filter_var(), preg_match(), or other validation logic on the 'id' parameterAffected if No input validation or sanitization is performed on the 'id' GET parameter before exec()
If speechmac.php exists and contains exec($_GET['id']) without any sanitization, the environment is vulnerable to CVE-2026-34112 and allows unauthenticated command injection.
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 on the 'id' parameter and use PHP's escapeshellarg() function to sanitize all user input before passing it to exec(), or refactor the code to avoid shell execution entirely.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34112 — 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-34112 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