CVE-2017-8835

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 62%
CISA-KEV: Not listedEPSS: 62%CVSS: 9.8Exploit: NoneExposed: 0

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

SQL injection exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before fw-b305hw2_380hw6_580hw2_710hw3_1350hw2_2500-7.0.1-build2093. An attack vector is the bauth cookie to cgi-bin/MANGA/admin.cgi. One impact is enumeration of user accounts by observing whether a session ID can be retrieved from the sessions database.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.1%
KEV
Not listed

Published

June 5, 2017

Last Modified

May 13, 2026

Advisory Details (3)

Auto-updated Jun 21, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Advisory X41-2017-005: Multiple Vulnerabilities in Peplink Balance Routers | X41 D-Sec - Penetration Tests and Source Code Audits

https://www.x41-dsec.de/lab/advisories/x41-2017-005-peplink/
generic🟡 PoC Available

Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure - CGI webapps Exploit

https://www.exploit-db.com/exploits/42130/
generic

Bugtraq: X41-2017-005 - Multiple Vulnerabilities in peplink balance routers

http://seclists.org/bugtraq/2017/Jun/1

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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-06 16:24 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-05 02:27 UTCEPSS rescore
  4. 2026-07-02 16:54 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-27 03:06 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-22 14:23 UTCEPSS rescore
  15. 2026-06-22 14:23 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-19 19:23 UTCEPSS rescore
  19. 2026-06-19 19:23 UTCEPSS rescore
  20. 2026-06-18 17:50 UTCEPSS rescore
  21. 2026-06-17 17:50 UTCEPSS rescore
  22. 2026-06-16 17:50 UTCEPSS rescore
  23. 2026-06-15 17:45 UTCEPSS rescore
  24. 2026-06-13 22:58 UTCEPSS rescore
  25. 2026-06-13 22:57 UTCEPSS rescore
Show 60 more
  1. 2026-06-12 23:09 UTCEPSS rescore
  2. 2026-06-12 23:09 UTCEPSS rescore
  3. 2026-06-11 13:57 UTCEPSS rescore
  4. 2026-06-10 22:15 UTCEPSS rescore
  5. 2026-06-10 13:19 UTCEPSS rescore
  6. 2026-06-07 15:22 UTCEPSS rescore
  7. 2026-06-07 15:22 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-06-05 22:44 UTCEPSS rescore
  11. 2026-06-05 22:44 UTCEPSS rescore
  12. 2026-06-05 06:08 UTCEPSS rescore
  13. 2026-06-05 06:08 UTCEPSS rescore
  14. 2026-06-04 13:10 UTCEPSS rescore
  15. 2026-06-04 13:10 UTCEPSS rescore
  16. 2026-06-02 20:11 UTCEPSS rescore
  17. 2026-06-02 20:11 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 00:14 UTCEPSS rescore
  21. 2026-05-31 00:14 UTCEPSS rescore
  22. 2026-05-29 13:41 UTCEPSS rescore
  23. 2026-05-27 13:38 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-22 21:15 UTCEPSS rescore
  26. 2026-05-22 21:15 UTCEPSS rescore
  27. 2026-05-22 21:15 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 22:37 UTCEPSS rescore
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-20 22:37 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 22:37 UTCEPSS rescore
  41. 2026-05-20 08:07 UTCEG score recompute
  42. 2026-05-20 08:07 UTCGHSA enrichment
  43. 2026-05-20 04:04 UTCEG score recompute
  44. 2026-05-20 04:04 UTCGHSA enrichment
  45. 2026-05-20 00:02 UTCEG score recompute
  46. 2026-05-20 00:02 UTCGHSA enrichment
  47. 2026-05-19 20:00 UTCEG score recompute
  48. 2026-05-19 20:00 UTCGHSA enrichment
  49. 2026-05-19 15:58 UTCEG score recompute
  50. 2026-05-19 15:58 UTCGHSA enrichment
  51. 2026-05-19 11:55 UTCEG score recompute
  52. 2026-05-19 11:55 UTCGHSA enrichment
  53. 2026-05-19 07:53 UTCEG score recompute
  54. 2026-05-19 07:53 UTCGHSA enrichment
  55. 2026-05-19 03:51 UTCEG score recompute
  56. 2026-05-19 03:51 UTCGHSA enrichment
  57. 2026-05-18 23:49 UTCEG score recompute
  58. 2026-05-18 21:30 UTCEPSS rescore
  59. 2026-05-18 21:30 UTCEPSS rescore
  60. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-42130
    First seen Jun 6, 2017

    Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure

    Open source ↗
  • Metasploitauxiliary/gather/peplink_bauth_sqli✓ verified
    First seen Jan 1, 2017

    Peplink Balance routers SQLi

    Open source ↗

Frequently asked(5)

What is CVE-2017-8835?
CVE-2017-8835 is a critical vulnerability published on June 5, 2017. SQL injection exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before fw-b305hw2380hw6580hw2710hw31350hw2_2500-7.0.1-build2093. An attack vector is the bauth cookie to cgi-bin/MANGA/admin.cgi. One impact is enumeration of user accounts by observing whether a…
When was CVE-2017-8835 disclosed?
CVE-2017-8835 was first published in the National Vulnerability Database on June 5, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8835 actively exploited?
CVE-2017-8835 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-8835?
CVE-2017-8835 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-8835?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8835, 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-2017-8835

Explore →

Is Your Infrastructure Affected by CVE-2017-8835?

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

Start Free Scan →Browse All CVEs