CVE-2017-8835: SQL injection exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…
Noroxi assessment
Priority: This week (action score 60/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
- Probability of exploitation in the next 30 days: 63.2% (FIRST EPSS); higher than 99.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 5, 2017
- Updated
- Jun 16, 2026
- EPSS
- 63.2% · 99th percentile
- CWE
- CWE-89
Report tools
Action score
60
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 19 / 30 · 63.2%
- Ready-made attack tool
- 2 / 60 · floor: at least 60
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| peplink | b305hw2 firmware | cpe:2.3:o:peplink:b305hw2_firmware |
| peplink | balance 305 | cpe:2.3:h:peplink:balance_305 |
| peplink | 380hw6 firmware | cpe:2.3:o:peplink:380hw6_firmware |
| peplink | balance 380 | cpe:2.3:h:peplink:balance_380 |
| peplink | 580hw2 firmware | cpe:2.3:o:peplink:580hw2_firmware |
| peplink | balance 580 | cpe:2.3:h:peplink:balance_580 |
| peplink | 710hw3 firmware | cpe:2.3:o:peplink:710hw3_firmware |
| peplink | balance 710 | cpe:2.3:h:peplink:balance_710 |
| peplink | 1350hw2 firmware | cpe:2.3:o:peplink:1350hw2_firmware |
| peplink | balance 1350 | cpe:2.3:h:peplink:balance_1350 |
| peplink | 2500 firmware | cpe:2.3:o:peplink:2500_firmware |
| peplink | balance 2500 | cpe:2.3:h:peplink:balance_2500 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- peplink 1350hw2 firmware7.0.1
- peplink 2500 firmware7.0.1
- peplink 380hw6 firmware7.0.1
- peplink 580hw2 firmware7.0.1
- peplink 710hw3 firmware7.0.1
- peplink b305hw2 firmware7.0.1
Same product
peplink: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-8837Cleartext password storage exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…40Plan
- CVE-2017-8836CSRF exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…36Monitor
- CVE-2017-8841Arbitrary file deletion exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…33Monitor
Published before and after this one in the same product
- Later →CVE-2017-8838Jun 5, 2017 · XSS via syncid exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…25Monitor
- Later →CVE-2017-8839Jun 5, 2017 · XSS via orig_url exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…25Monitor
- Later →CVE-2017-8840Jun 5, 2017 · Debug information disclosure exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Exploit-DB entry ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2017-06-06 |
| Exploit-DB entry | webapps | 2017-06-06 |
| Exploit-DB entry | webapps | 2017-06-06 |
| Metasploit module | auxiliary/gather/peplink_bauth_sqliPeplink Balance routers SQLiauxiliary | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+1 d
- TodayNov 16, 2026+3451 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.