Archer BE230 v1.2: Improper Neutralization of Special Elements used in an OS Command
CVE-2026-0631 is a high-severity improper neutralization of special elements used in an OS command vulnerability in Archer BE230 v1.2 from TP-Link, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists version 1.2.4 Build 20251218 rel.70420 as the first without the flaw, so updating Archer BE230 v1.2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.62% chance of exploitation within 30 days, higher than 77% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Archer BE230 v1.2 to 1.2.4 Build 20251218 rel.70420 or a later version.
- Update Archer AXE75 v1 to 1.5.6 Build 20260623 or a later version.
- Update Archer BE3600 v1 to (KR)_V1_1.2.2 Build 20260903 or (EU)_V1_1.2.6 Build 20260617 or (USW)_V1.26_1.2.6 Build 20260617, whichever matches your release line, or a later version.
- Read the advisory on tp-link.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| TP-Link | Archer BE230 v1.2 | before 1.2.4 Build 20251218 rel.70420 | 1.2.4 Build 20251218 rel.70420 |
| TP-Link | Archer AXE75 v1 | before 1.5.6 Build 20260623 | 1.5.6 Build 20260623 |
| TP-Link | Archer BE3600 v1 | before (KR)_V1_1.2.2 Build 20260903; before (EU)_V1_1.2.6 Build 20260617; before (USW)_V1.26_1.2.6 Build 20260617 | (KR)_V1_1.2.2 Build 20260903, (EU)_V1_1.2.6 Build 20260617, (USW)_V1.26_1.2.6 Build 20260617 |
| TP-Link | Archer AX10 v3 | before V3_1.3.3 Build 20260616 | V3_1.3.3 Build 20260616 |
| TP-Link | Archer Be230 Firmware | before 1.2.4 | 1.2.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.5 | High | CNA |
| CVSS 3.1 | 8.0 | High | NVD |
Official description
An OS Command Injection vulnerability exists in the Surfshark VPN login functionality in TP-Link Archer BE230 v1.2, BE3600v1, AX10 v3 and AXE75 v1, allowing an adjacent authenticated attacker to execute arbitrary code. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID. This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420 and Archer AXE75 v1 < 1.5.6 Build 20260623.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an OS Command
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Improper Neutralization of Special Elements used in an OS Command vulnerabilities (CWE-78)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- tp-link.com/en/support/download/archer-ax10/v3/#Firmware
- tp-link.com/en/support/download/archer-axe75/v1/#Firmware
- tp-link.com/en/support/download/archer-be230/v1.20/#FirmwareProduct
- tp-link.com/en/support/download/archer-be3600/v1/#Firmware
- tp-link.com/kr/support/download/archer-be3600/v1/#Firmware
- tp-link.com/sg/support/download/archer-be230/v1.20/#FirmwareProduct
- tp-link.com/us/support/download/archer-ax10/v3/#Firmware
- tp-link.com/us/support/download/archer-axe75/v1/#Firmware
- tp-link.com/us/support/download/archer-be230/v1.20/#FirmwareProduct
- tp-link.com/us/support/download/archer-be3600/v1.26/#Firmware
Other vulnerabilities in Archer BE230 v1.2
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
- 8.0 High severity
Recent Improper Neutralization of Special Elements used in an OS Command vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 8.0 High severity
- 8.0 High severity
- 8.0 High severity
- 8.0 High severity
Spotted an error? Tell us.