The storage endpoint /storage/upload of cjbi admin3 v3.0.0 are missing permission checks. /Any logged-in user can upload arbitrary files, and any anonymous attacker can download them.
CVE-2026-75339
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; 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
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 56(Track*)EG Risk 56/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 computedSeverity88% × 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 (1)
Auto-updated Aug 28, 2026CVE/admin3/file.md at main · fangtang7/CVE · GitHub
https://github.com/fangtang7/CVE/blob/main/admin3/file.mdVendor Advisories for CVE-2026-75339(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 19:13 UTCGHSA enrichment
- 2026-08-29 07:58 UTCEG score recompute
- 2026-08-29 07:58 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:44 UTCEG score recompute
- 2026-08-28 20:43 UTCGHSA enrichment
- 2026-08-28 19:42 UTCEG score recompute▲ 8.80
- 2026-08-28 19:42 UTCGHSA enrichment
- 2026-08-28 19:36 UTCMITRE cvelistV5CVSS v3 → 8.8 · 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:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-75339?
When was CVE-2026-75339 disclosed?
Is CVE-2026-75339 actively exploited?
What is the CVSS score of CVE-2026-75339?
How do I remediate CVE-2026-75339?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75339
Is Your Infrastructure Affected by CVE-2026-75339?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.