CVE-2026-82699

LOWPre-NVD 2.72.7—
EchelonGraph scoreHIGH confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-08-31. a secondary CVSS source baseline 2.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: Elevated riskExposed: 0

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

A flaw has been found in sambitraj Student Management System up to 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5. This impacts an unknown function of the file aca.sql of the component Password Handler. Executing a manipulation of the argument Password can lead to cleartext storage of sensitive information. The attack can be executed remotely. The exploit has been published and may be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable.

CVSS v3
2.7
EG Score
2.7(high)
EG Risk
28(Track)
EG Risk 28/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 computed
Severity27% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 31, 2026

Last Modified

August 31, 2026

References (6)

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82699?
CVE-2026-82699 is a low vulnerability published on August 31, 2026. A flaw has been found in sambitraj Student Management System up to 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5. This impacts an unknown function of the file aca.sql of the component Password Handler. Executing a manipulation of the argument Password can lead to cleartext storage of sensitive…
When was CVE-2026-82699 disclosed?
CVE-2026-82699 was first published in the National Vulnerability Database on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82699 actively exploited?
CVE-2026-82699 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 95.1% of all scored CVEs.
What is the CVSS score of CVE-2026-82699?
CVE-2026-82699 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2026-82699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82699, 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-82699

Explore →

Is Your Infrastructure Affected by CVE-2026-82699?

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

Start Free Scan →Browse All CVEs