CVE-2026-16324

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: Elevated riskExposed: 0

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

A vulnerability was identified in Metasoft 美特软件 MetaCRM up to 6.4.0 Beta06. The impacted element is an unknown function of the file /business/qnaire/upload.jsp. Such manipulation of the argument File leads to unrestricted upload. The attack may be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
64(Attend)
EG Risk 64/100SSVC: Attend

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 computed
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 22, 2026

References (5)

Vendor Advisories for CVE-2026-16324(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 37× 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-31 00:29 UTCEG score recompute
  2. 2026-07-31 00:29 UTCGHSA enrichment
  3. 2026-07-30 13:31 UTCEG score recompute
  4. 2026-07-30 13:31 UTCGHSA enrichment
  5. 2026-07-30 02:31 UTCEG score recompute
  6. 2026-07-30 02:31 UTCGHSA enrichment
  7. 2026-07-30 01:30 UTCEPSS rescore
  8. 2026-07-29 15:35 UTCGHSA enrichment
  9. 2026-07-29 04:36 UTCGHSA enrichment
  10. 2026-07-28 17:38 UTCEG score recompute
  11. 2026-07-28 17:37 UTCGHSA enrichment
  12. 2026-07-28 06:37 UTCGHSA enrichment
  13. 2026-07-27 19:39 UTCEG score recompute
  14. 2026-07-27 19:39 UTCGHSA enrichment
  15. 2026-07-27 14:13 UTCEPSS rescore
  16. 2026-07-27 08:39 UTCGHSA enrichment
  17. 2026-07-26 21:42 UTCEG score recompute
  18. 2026-07-26 21:42 UTCGHSA enrichment
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 10:45 UTCEG score recompute
  22. 2026-07-26 10:45 UTCGHSA enrichment
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
Show 12 more
  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 23:27 UTCEG score recompute
  4. 2026-07-22 23:27 UTCGHSA enrichment
  5. 2026-07-22 16:51 UTCNVD updateCVSS v4 → 5.5
  6. 2026-07-22 14:46 UTCMITRE cvelistV5CVSS v4 → 6.9
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:24 UTCEPSS rescore
  9. 2026-07-20 22:42 UTCEG score recompute
  10. 2026-07-20 22:41 UTCNVD updateCVSS v4 → 5.5
  11. 2026-07-20 21:47 UTCEG score recompute
  12. 2026-07-20 21:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16324?
CVE-2026-16324 is a high vulnerability published on July 20, 2026. A vulnerability was identified in Metasoft 美特软件 MetaCRM up to 6.4.0 Beta06. The impacted element is an unknown function of the file /business/qnaire/upload.jsp. Such manipulation of the argument File leads to unrestricted upload. The attack may be launched remotely. The exploit is publicly…
When was CVE-2026-16324 disclosed?
CVE-2026-16324 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16324 actively exploited?
CVE-2026-16324 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.9% of all scored CVEs.
What is the CVSS score of CVE-2026-16324?
CVE-2026-16324 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-16324?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16324, 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-16324

Explore →

Is Your Infrastructure Affected by CVE-2026-16324?

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

Start Free Scan →Browse All CVEs