dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-34106

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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 · unedited
Guardian language-system passes the id GET parameter directly into a PHP exec() call in subtitles.php (line 19) without sanitization: exec(\"php jobs/subtitle_rendering.php \".$login_session.\" \".$_GET['id'].\" ...\"). No authentication is required. An unauthenticated remote attacker can append shell metacharacters to the id parameter 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 confidence

Critical command injection vulnerability in Guardian language-system's subtitles.php where the id GET parameter is passed directly to PHP's exec() function without sanitization. Unauthenticated attackers can inject shell metacharacters to execute arbitrary OS commands.

MitigationImplement strict input validation and sanitization for the id parameter before use in exec(), preferably using a whitelist approach or proper shell escaping functions. Additionally, enforce authentication on the affected endpoint.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the subtitles.php file
    Search the web server document root for a file named subtitles.php, typically found in language-system or language processing modules of Guardian. Use: find /var/www -name subtitles.php 2>/dev/null or similar directory search command.
    Affected if The file exists and is web-accessible in the application's web directory.
  2. Identify Guardian language-system installation
    Determine if the system has Guardian language-system installed by checking for its typical installation directory structure, composer.json, or framework indicators. Compare any found version against the vendor's release history if version information is exposed.
    Affected if Guardian language-system is installed and running.
  3. Verify web accessibility of subtitles.php
    Confirm the subtitles.php file is accessible via HTTP/HTTPS by attempting to access it through the web server (e.g., curl http://TARGET/path/to/subtitles.php). The vulnerability is exploitable remotely without authentication.
    Affected if The file responds to HTTP requests and is not protected by authentication or access controls.
  4. Review the id parameter handling in subtitles.php
    Examine the source code of subtitles.php for the exec() call and verify whether the 'id' GET parameter is passed directly to exec() without sanitization, validation, or escaping. Look for patterns like exec($_GET['id']) or exec(...$_GET['id']....).
    Affected if The code shows the 'id' parameter being passed to exec() without any sanitization, validation, or use of escapeshellcmd/escapeshellarg.
  5. Check PHP execution functions are enabled
    Review php.ini or use phpinfo() to confirm that exec(), shell_exec(), and related functions are not disabled via disable_functions setting. Check if the PHP process has permissions to execute system commands.
    Affected if exec() function is enabled and available to the PHP script.

A user is affected if Guardian language-system is installed with a web-accessible subtitles.php that passes the 'id' GET parameter directly to exec() without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for the id parameter before use in exec(), preferably using a whitelist approach or proper shell escaping functions. Additionally, enforce authentication on the affected endpoint.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34106 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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