CVE-2026-34111
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_text.php (line 18) without sanitization: exec(\"php jobs/speech_audio_mac_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 speechmac_text.php where the 'id' GET parameter is passed directly to PHP's exec() function without any sanitization or validation. An unauthenticated remote attacker can inject shell metacharacters to execute arbitrary OS commands with the privileges of the web server process.
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 Guardian language-system installationSearch the filesystem for speechmac_text.php or directories named 'guardian' or 'language-system'. Common paths may include /var/www/, /home/*/public_html/, or C:\inetpub\wwwroot\ on Windows servers.Affected if The Guardian language-system software is found on the server
-
Identify the vulnerable PHP fileConfirm the presence of speechmac_text.php in the installation directory. This is the file containing the command injection flaw.Affected if speechmac_text.php exists in the application directory
-
Examine the source code for vulnerable exec() usageOpen speechmac_text.php and search for exec( or shell_exec( functions. Look for $_GET['id'] being passed directly as an argument without sanitization functions like escapeshellarg() or preg_replace().Affected if The code contains exec() or shell_exec() with $_GET['id'] as a parameter without input sanitization
-
Verify the application is accessible via webAttempt to access speechmac_text.php via HTTP (e.g., curl http://target/path/speechmac_text.php). The vulnerability is exploitable remotely if the file is web-accessible.Affected if The file is reachable over the network and accepts user-supplied 'id' parameter
The environment is affected if the Guardian language-system is installed, speechmac_text.php exists, and the 'id' GET parameter is passed directly to exec() without sanitization functions.
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/sanitization on the 'id' parameter before passing to exec(), or better yet, refactor to avoid shell execution entirely by using parameterized approaches. Additionally, implement authentication requirements for the affected endpoint.
- 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-34111 — 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-34111 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