A security vulnerability has been detected in weiqingwen spring-boot-forum up to 538eecc3c6b85fdf0768ab4e8354b48c0c17d94f. Affected is the function validate of the file src/main/java/com/qingwenwei/util/NewUserFormValidator.java of the component Avatar Upload. The manipulation of the argument Username leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-96678
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(low)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (1)
Auto-updated Sep 23, 2026spring-boot-forum has a path traversal vulnerability that allows arbitrary file overwriting · Issue #3 · ssiled/cve · GitHub
https://github.com/ssiled/cve/issues/3Vendor Advisories for CVE-2026-96678(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 4× in last 7d / 4× 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-09-23 23:24 UTCEG score recompute
- 2026-09-23 23:24 UTCNVD updateCVSS v4 → 2.1
- 2026-09-23 22:56 UTCEG score recompute
- 2026-09-23 22:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22
- CVE-2026-85706EG 10.0 KEVEPSS p95CRITICAL
- CVE-2026-82954EG 9.9CRITICAL
- CVE-2026-8859EG 9.9CRITICAL
- CVE-2026-9559EG 9.9CRITICAL
- CVE-2026-96276EG 9.8CRITICAL
- CVE-2026-93616EG 9.8 KEVCRITICAL
- CVE-2026-89040EG 9.8CRITICAL
- CVE-2026-85661EG 9.8CRITICAL
- CVE-2026-82460EG 9.8CRITICAL
- CVE-2026-9181NVD 7.5EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-96678?
When was CVE-2026-96678 disclosed?
What is the CVSS score of CVE-2026-96678?
How do I remediate CVE-2026-96678?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96678
Is Your Infrastructure Affected by CVE-2026-96678?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.