CVE-2026-34117
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_to_subtitles.php (line 19) without sanitization: exec(\"php jobs/text_to_subtitles.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 OS command injection vulnerability in text_to_subtitles.php where the id GET parameter is passed directly to PHP's exec() function without any sanitization or escaping. An unauthenticated attacker can inject shell metacharacters to execute arbitrary operating system commands.
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 PHP fileSearch the web root and application directories for text_to_subtitles.php using: find /var/www -name 'text_to_subtitles.php' 2>/dev/null (Linux) or dir /s /b C:\*text_to_subtitles.php (Windows)Affected if The file exists in the application directory tree
-
Inspect code for vulnerable exec() usageOpen text_to_subtitles.php and examine lines containing exec(). Look for patterns like exec($_GET['id']) or exec(...$_GET['id']...) without escapeshellarg() or similar sanitizationAffected if The file contains exec() calls using $_GET['id'] directly without input sanitization
-
Verify web accessibilityCheck if the file is served via the web server by attempting to access it via HTTP/HTTPS (e.g., https://yourdomain/path/text_to_subtitles.php)Affected if The script is reachable via web requests (unauthenticated access is possible)
-
Confirm parameter handlingReview how the 'id' parameter is processed - verify it is taken directly from $_GET['id'] and passed to exec() without any validation or escaping functionsAffected if The 'id' GET parameter flows to exec() without sanitization such as escapeshellarg()
If text_to_subtitles.php exists, is web-accessible, and uses the 'id' GET parameter in exec() without sanitization, 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 dataImmediately remove or sanitize the id parameter before passing to exec(), implement allowlist validation for expected input values, and use proper command escaping functions or parameterized approaches instead of string concatenation.
- 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-34117 — 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-34117 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