CVE-2026-34116
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 transcribe.php (line 15) without sanitization: exec(\"php jobs/transcribe.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 confidenceCommand injection vulnerability in Guardian language-system's transcribe.php where the 'id' GET parameter is passed unsanitized to a PHP exec() call. An unauthenticated remote attacker can inject shell metacharacters to execute arbitrary OS commands with the privileges of the web 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 transcribe.php in the web applicationSearch the web root and application directories for a file named transcribe.php using file system search commands (e.g., find, ls, or directory listing tools).Affected if The file transcribe.php exists in the application directory tree.
-
Verify exec() usage in transcribe.phpOpen transcribe.php and search for instances of the exec() function or similar shell execution functions (system, shell_exec, passthru).Affected if The file contains exec() or related shell execution functions.
-
Inspect 'id' parameter handlingExamine how the 'id' GET parameter is retrieved (e.g., $_GET['id']) and trace its usage through the code to see if it flows into exec() calls.Affected if The 'id' GET parameter is passed directly to exec() without sanitization.
-
Confirm absence of input sanitizationCheck whether the 'id' parameter is processed through sanitization functions such as escapeshellarg(), escapeshellcmd(), or other input validation before reaching exec().Affected if The 'id' parameter is NOT sanitized with escapeshellarg() or equivalent before being used in exec().
The environment is affected if transcribe.php exists and uses the 'id' GET parameter in an exec() call without proper input sanitization using escapeshellarg() or equivalent.
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 dataImmediately restrict access to transcribe.php or disable the vulnerable functionality until a patch can be applied. Implement proper input validation/sanitization to prevent shell metacharacter injection, ideally by avoiding exec() calls with user input entirely.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34116 — 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-34116 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