Authentication Bypass via Hardcoded Master Verification Code vulnerability in Siam Ordering (siam-server) 1.0.0 allows remote unauthenticated attackers to log in as any user, merchant, or administrator.
CVE-2026-71809
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; 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.1
- EG Score
- 8.1(high)
- EG Risk
- 52(Track*)EG Risk 52/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 computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 14, 2026
Advisory Details (1)
Auto-updated Sep 14, 2026Authentication Bypass via Hardcoded Universal Master SMS Verification Code ("123456") · Issue #11 · W000i/vuln · GitHub
https://github.com/W000i/vuln/issues/11Vendor Advisories for CVE-2026-71809(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 28× 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.
- 2026-09-19 04:43 UTCEG score recompute
- 2026-09-19 04:43 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 17:54 UTCGHSA enrichment
- 2026-09-18 07:05 UTCGHSA enrichment
- 2026-09-17 20:16 UTCEG score recompute
- 2026-09-17 20:16 UTCGHSA enrichment
- 2026-09-17 08:24 UTCGHSA enrichment
- 2026-09-16 21:33 UTCEG score recompute
- 2026-09-16 21:33 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 10:43 UTCEG score recompute
- 2026-09-16 10:43 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 23:50 UTCGHSA enrichment
- 2026-09-15 13:01 UTCEG score recompute
- 2026-09-15 13:01 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 02:11 UTCEG score recompute
- 2026-09-15 02:11 UTCGHSA enrichment
- 2026-09-14 15:22 UTCEG score recompute
- 2026-09-14 15:22 UTCGHSA enrichment
- 2026-09-14 14:25 UTCEG score recompute▲ 8.10
- 2026-09-14 14:25 UTCGHSA enrichment
- 2026-09-14 14:24 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
Show 8 moreShow fewer
- 2026-09-13 11:33 UTCEG score recompute
- 2026-09-13 11:33 UTCGHSA enrichment
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 15:59 UTCGHSA enrichment
- 2026-09-09 23:31 UTCNVD update
- 2026-09-09 22:20 UTCEG score recompute
- 2026-09-09 22:19 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71809?
When was CVE-2026-71809 disclosed?
Is CVE-2026-71809 actively exploited?
What is the CVSS score of CVE-2026-71809?
How do I remediate CVE-2026-71809?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71809
Is Your Infrastructure Affected by CVE-2026-71809?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.