WAVLINK WN536AX6-A V260507 OpenVPN /protocol.csp strcpy openvpn_ip stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 1.62 |
Summary
A vulnerability was found in WAVLINK WN536AX6-A V260507. It has been rated as very critical. This impacts the function strcpy of the file /protocol.csp of the component OpenVPN Handler. This manipulation of the argument openvpn_ip causes stack-based overflow.
This vulnerability is registered as CVE-2026-120281. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
The vendor was contacted early about this disclosure.
Details
A vulnerability classified as very critical was found in WAVLINK WN536AX6-A V260507. Affected by this vulnerability is the function strcpy of the file /protocol.csp of the component OpenVPN Handler. The manipulation of the argument openvpn_ip with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-120281. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/01/2026).
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.1
VulDB Base Score: 10.0
VulDB Temp Score: 9.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/01/2026 Advisory disclosed11/01/2026 VulDB entry created
11/01/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CNA: VulDB
CVE: CVE-2026-120281 (🔒)
GCVE (CVE): GCVE-0-2026-120281
GCVE (VulDB): GCVE-100-429625
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/01/2026 08:49Updated: 11/01/2026 14:27
Changes: 11/01/2026 08:49 (58), 11/01/2026 14:27 (1)
Complete: 🔍
Submitter: yyjy
Cache ID: 216::103
Submit
Accepted
- Submit #919790: Wavlink WN536AX6 V260507 CWE-121 (by yyjy)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.