CVE-2026-34105

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Guardian language-system passes the id GET parameter directly into an unsanitized SQL query in translate_text.php (line 15): SELECT id, filename, extension, type FROM files where id = '\".$_GET['id'].\"'. An authenticated attacker can perform error-based SQL injection to extract database contents.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
29.3%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
No patch confirmed yet.
generic

Guardian Language-System Unauthenticated SQL Injection via id Parameter in translate_text.php | Advisories | VulnCheck

https://www.vulncheck.com/advisories/guardian-language-system-unauthenticated-sql-injection-via-id-parameter-in-translate-text-php

Vendor Advisories for CVE-2026-34105(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 05:13 UTCEG score recompute
  2. 2026-07-07 05:13 UTCGHSA enrichment
  3. 2026-07-07 01:20 UTCEG score recompute
  4. 2026-07-07 01:20 UTCGHSA enrichment
  5. 2026-07-06 21:31 UTCEG score recompute
  6. 2026-07-06 21:31 UTCGHSA enrichment
  7. 2026-07-06 17:42 UTCEG score recompute
  8. 2026-07-06 17:42 UTCGHSA enrichment
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 13:53 UTCEG score recompute
  12. 2026-07-06 13:52 UTCGHSA enrichment
  13. 2026-07-06 10:03 UTCEG score recompute
  14. 2026-07-06 10:02 UTCGHSA enrichment
  15. 2026-07-06 06:11 UTCEG score recompute
  16. 2026-07-06 06:11 UTCGHSA enrichment
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:20 UTCEG score recompute
  20. 2026-07-06 02:20 UTCGHSA enrichment
  21. 2026-07-05 22:31 UTCEG score recompute
  22. 2026-07-05 22:31 UTCGHSA enrichment
  23. 2026-07-05 18:42 UTCEG score recompute
  24. 2026-07-05 18:42 UTCGHSA enrichment
  25. 2026-07-05 14:53 UTCEG score recompute
Show 52 more
  1. 2026-07-05 14:53 UTCGHSA enrichment
  2. 2026-07-05 11:04 UTCEG score recompute
  3. 2026-07-05 11:03 UTCGHSA enrichment
  4. 2026-07-05 07:14 UTCEG score recompute
  5. 2026-07-05 07:14 UTCGHSA enrichment
  6. 2026-07-05 03:26 UTCEG score recompute
  7. 2026-07-05 03:26 UTCGHSA enrichment
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 23:37 UTCEG score recompute
  10. 2026-07-04 23:37 UTCGHSA enrichment
  11. 2026-07-04 19:48 UTCEG score recompute
  12. 2026-07-04 19:48 UTCGHSA enrichment
  13. 2026-07-04 15:59 UTCEG score recompute
  14. 2026-07-04 15:59 UTCGHSA enrichment
  15. 2026-07-04 12:09 UTCEG score recompute
  16. 2026-07-04 12:09 UTCGHSA enrichment
  17. 2026-07-04 08:20 UTCEG score recompute
  18. 2026-07-04 08:20 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 04:29 UTCEG score recompute
  21. 2026-07-04 04:29 UTCGHSA enrichment
  22. 2026-07-04 00:35 UTCEG score recompute
  23. 2026-07-04 00:35 UTCGHSA enrichment
  24. 2026-07-03 20:44 UTCEG score recompute
  25. 2026-07-03 20:44 UTCGHSA enrichment
  26. 2026-07-03 16:56 UTCEG score recompute
  27. 2026-07-03 16:55 UTCGHSA enrichment
  28. 2026-07-03 13:07 UTCEG score recompute
  29. 2026-07-03 13:07 UTCGHSA enrichment
  30. 2026-07-03 09:18 UTCEG score recompute
  31. 2026-07-03 09:17 UTCGHSA enrichment
  32. 2026-07-03 05:28 UTCEG score recompute
  33. 2026-07-03 05:28 UTCGHSA enrichment
  34. 2026-07-03 01:38 UTCEG score recompute
  35. 2026-07-03 01:38 UTCGHSA enrichment
  36. 2026-07-02 21:48 UTCEG score recompute
  37. 2026-07-02 21:48 UTCGHSA enrichment
  38. 2026-07-02 17:59 UTCEG score recompute
  39. 2026-07-02 17:59 UTCGHSA enrichment
  40. 2026-07-02 16:58 UTCNVD updateCVSS v4 → 9.3
  41. 2026-07-02 14:10 UTCEG score recompute
  42. 2026-07-02 14:10 UTCGHSA enrichment
  43. 2026-07-02 10:22 UTCEG score recompute
  44. 2026-07-02 10:22 UTCGHSA enrichment
  45. 2026-07-02 06:33 UTCEG score recompute
  46. 2026-07-02 06:33 UTCGHSA enrichment
  47. 2026-07-02 02:42 UTCEG score recompute
  48. 2026-07-02 02:42 UTCGHSA enrichment
  49. 2026-07-01 22:53 UTCEG score recompute
  50. 2026-07-01 22:53 UTCGHSA enrichment
  51. 2026-07-01 19:03 UTCEG score recompute
  52. 2026-07-01 19:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-34105?
CVE-2026-34105 is a critical vulnerability published on July 1, 2026. Guardian language-system passes the id GET parameter directly into an unsanitized SQL query in translatetext.php (line 15): SELECT id, filename, extension, type FROM files where id = '\".$GET['id'].\"'. An authenticated attacker can perform error-based SQL injection to extract database contents.
When was CVE-2026-34105 disclosed?
CVE-2026-34105 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34105 actively exploited?
CVE-2026-34105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-34105?
CVE-2026-34105 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-34105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34105, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-34105

Explore →

Is Your Infrastructure Affected by CVE-2026-34105?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.