A SQL injection vulnerability was found in YzmCMS 7.5. The issue occurs in the get_arrchildid() function within application/admin/controller/category.class.php, where the user-controlled parentid parameter is concatenated directly into a FIND_IN_SET() SQL clause without proper sanitization. This allows an authenticated administrator to execute arbitrary SQL queries via boolean-based blind injection, potentially leading to full database compromise.
CVE-2026-75417
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EG Risk
- 48(Track*)EG Risk 48/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026TKar0-CvePoc/2026-CVE-POC/CVE-2026-75417 at main · TKar0/TKar0-CvePoc · GitHub
https://github.com/TKar0/TKar0-CvePoc/tree/main/2026-CVE-POC/CVE-2026-75417GitHub - yzmcms/yzmcms: YzmCMS是一款基于YZMPHP开发的一套轻量级开源内容管理系统,YzmCMS简洁、安全、开源、实用,可运行在Linux、Windows、MacOSX、Solaris等各种平台上,专注为公司企业、个人站长快速建站提供解决方案。 · GitHub
https://github.com/yzmcms/yzmcmsVendor Advisories for CVE-2026-75417(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 14× in last 7d / 14× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:25 UTCGHSA enrichment
- 2026-08-29 08:34 UTCEG score recompute
- 2026-08-29 08:34 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:44 UTCEG score recompute
- 2026-08-28 20:44 UTCGHSA enrichment
- 2026-08-28 19:42 UTCEG score recompute▲ 7.20
- 2026-08-28 19:42 UTCGHSA enrichment
- 2026-08-28 19:36 UTCMITRE cvelistV5CVSS v3 → 7.2 · severity → HIGH
- 2026-08-28 00:32 UTCGHSA enrichment
- 2026-08-28 00:26 UTCNVD update
- 2026-08-27 23:24 UTCEG score recompute
- 2026-08-27 23:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-75417?
When was CVE-2026-75417 disclosed?
Is CVE-2026-75417 actively exploited?
What is the CVSS score of CVE-2026-75417?
How do I remediate CVE-2026-75417?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75417
Is Your Infrastructure Affected by CVE-2026-75417?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.