CVE-2026-57920: CWE-551 Incorrect Behavior Order: Authorization Before Parsing and Canonicalization in Peplink InControl
Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a semicolon to bypass access-control rules for certain /rest/o/{orgId} endpoints.
AI Analysis
Technical Summary
This vulnerability in Peplink InControl versions 2 through 2.14.2 before 2026-06-03 arises from improper ordering of authorization checks before parsing and canonicalization of input. Specifically, the use of a semicolon in requests to certain /rest/o/{orgId} endpoints can bypass access-control rules. This is categorized as CWE-551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization). The CVSS 3.1 base score is 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), reflecting network attack vector, low attack complexity, requiring low privilege, no user interaction, scope change, and high confidentiality impact.
Potential Impact
Successful exploitation allows an attacker with low privileges to bypass access controls on specific REST API endpoints, potentially exposing sensitive organizational data (confidentiality impact). There is no impact on integrity or availability. The vulnerability affects confidentiality with a scope change, meaning the attacker can access resources beyond their authorization level.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is documented in the provided data. Until a patch is available, restrict access to the affected endpoints and monitor for suspicious use of semicolons in request URLs as a potential indicator of exploitation attempts.
CVE-2026-57920: CWE-551 Incorrect Behavior Order: Authorization Before Parsing and Canonicalization in Peplink InControl
Description
Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a semicolon to bypass access-control rules for certain /rest/o/{orgId} endpoints.
CVSS v3.1
Score 7.7high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Peplink InControl versions 2 through 2.14.2 before 2026-06-03 arises from improper ordering of authorization checks before parsing and canonicalization of input. Specifically, the use of a semicolon in requests to certain /rest/o/{orgId} endpoints can bypass access-control rules. This is categorized as CWE-551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization). The CVSS 3.1 base score is 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), reflecting network attack vector, low attack complexity, requiring low privilege, no user interaction, scope change, and high confidentiality impact.
Potential Impact
Successful exploitation allows an attacker with low privileges to bypass access controls on specific REST API endpoints, potentially exposing sensitive organizational data (confidentiality impact). There is no impact on integrity or availability. The vulnerability affects confidentiality with a scope change, meaning the attacker can access resources beyond their authorization level.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is documented in the provided data. Until a patch is available, restrict access to the affected endpoints and monitor for suspicious use of semicolons in request URLs as a potential indicator of exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-06-26T12:20:51.599Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3e72dccef61ccff96019c1
Added to database: 06/26/2026, 12:38:52 UTC
Last enriched: 06/26/2026, 12:53:33 UTC
Last updated: 08/09/2026, 12:41:11 UTC
Views: 92
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.