CVE-2026-78182

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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 security vulnerability has been detected in Shenzhen Gongji Technology XBROTHER Dynamic Environment Monitoring System up to 300R004C00B300. The affected element is the function PlanController.getImmediatePlans of the file /xbreport/api/v1/plamange/plansImmediate. The manipulation of the argument order/sort leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.

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
24%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 24, 2026

References (5)

Vendor Advisories for CVE-2026-78182(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 33× in last 7d / 33× 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-08-30 01:31 UTCEG score recompute
  2. 2026-08-30 01:31 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 13:03 UTCGHSA enrichment
  5. 2026-08-29 00:29 UTCEG score recompute
  6. 2026-08-29 00:28 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 09:46 UTCGHSA enrichment
  9. 2026-08-27 21:14 UTCEG score recompute
  10. 2026-08-27 21:14 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 08:46 UTCGHSA enrichment
  13. 2026-08-26 20:18 UTCEG score recompute
  14. 2026-08-26 20:18 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 07:50 UTCGHSA enrichment
  17. 2026-08-25 19:22 UTCEG score recompute
  18. 2026-08-25 19:22 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:52 UTCGHSA enrichment
  21. 2026-08-24 18:23 UTCEG score recompute
  22. 2026-08-24 18:23 UTCGHSA enrichment
  23. 2026-08-24 18:21 UTCNVD updateCVSS v4 → 5.5
  24. 2026-08-24 18:01 UTCEG score recompute
  25. 2026-08-24 18:01 UTCGHSA enrichment
Show 8 more
  1. 2026-08-24 18:01 UTCMITRE cvelistV5CVSS v4 → 6.9
  2. 2026-08-24 16:46 UTCEG score recompute
  3. 2026-08-24 16:46 UTCGHSA enrichment
  4. 2026-08-24 14:18 UTCEPSS rescore
  5. 2026-08-24 04:23 UTCEG score recompute
  6. 2026-08-24 04:21 UTCNVD updateCVSS v4 → 5.5
  7. 2026-08-24 03:51 UTCEG score recompute
  8. 2026-08-24 03:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78182?
CVE-2026-78182 is a high vulnerability published on August 24, 2026. A security vulnerability has been detected in Shenzhen Gongji Technology XBROTHER Dynamic Environment Monitoring System up to 300R004C00B300. The affected element is the function PlanController.getImmediatePlans of the file /xbreport/api/v1/plamange/plansImmediate. The manipulation of the argument…
When was CVE-2026-78182 disclosed?
CVE-2026-78182 was first published in the National Vulnerability Database on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78182 actively exploited?
CVE-2026-78182 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 76.4% of all scored CVEs.
What is the CVSS score of CVE-2026-78182?
CVE-2026-78182 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-78182?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78182, 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-78182

Explore →

Is Your Infrastructure Affected by CVE-2026-78182?

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

Start Free Scan →Browse All CVEs