PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-120238 WAVLINK CVE debrief

A vulnerability was found in WAVLINK WN553X1-B 260403_2.0.0, affecting the ovpn_file Handler's sub_4162A8 function in /bin/ioos, allowing for os command injection via the file_id argument. This issue can be exploited remotely. The CVE record was published on 2026-11-01T18:17:13.720Z and has not been modified since then. The vulnerability has a CVSS score of 8.6 and HIGH severity. Defenders should assess exposure and prioritize verification and remediation efforts. The ovpn_file Handler is a critical component, and exploitation could lead to unauthorized access or control.

Vendor
WAVLINK
Product
WN553X1-B
CVSS
HIGH 8.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-11-01
Original CVE updated
2026-11-01
Advisory published
2026-11-01
Advisory updated
2026-11-01

Who should care

Defenders responsible for WAVLINK WN553X1-B devices should assess exposure and potential impact, prioritizing verification and remediation efforts. This includes operators, platform administrators, vulnerability management teams, and security teams. The remote exploitation possibility and HIGH severity of the vulnerability necessitate immediate attention to prevent potential security breaches.

Why it matters

Defenders should prioritize verifying exposure of WAVLINK WN553X1-B devices and assessing potential impact, given the remote exploitation possibility and HIGH severity of the vulnerability.

  • Verify exposure of WAVLINK WN553X1-B devices to os command injection
  • Assess potential impact of remote exploitation
  • Monitor for exploitation attempts and anomalous activity
  • Review and apply vendor remediation if available

Technical summary

The WAVLINK WN553X1-B device has a vulnerability in the ovpn_file Handler's sub_4162A8 function, allowing for os command injection via the file_id argument. This issue can be exploited remotely, with a CVSS score of 8.6 and HIGH severity. The vulnerability affects the ovpn_file Handler, a critical component for VPN configuration. Exploitation could lead to unauthorized access or control, emphasizing the need for defenders to prioritize verification and remediation efforts. The technical details of the vulnerability require further analysis to understand its full impact.

Defensive priority

Defenders should prioritize verifying exposure of WAVLINK WN553X1-B devices and assessing potential impact, given the remote exploitation possibility.

Recommended defensive actions

  • Verify exposure of WAVLINK WN553X1-B devices
  • Assess potential impact of os command injection
  • Monitor for exploitation attempts
  • Review vendor remediation and apply patches if available
  • Track exceptions and retest remediated assets
  • Review compensating controls for exposed systems
  • Check relevant monitoring and detection logs

Evidence notes

The CVE record and NVD detail page provide information on the vulnerability. However, details on affected versions, exploitation, and remediation require further verification from official sources. The WAVLINK WN553X1-B device is a network device, and its exposure could have significant operational impacts. Defenders should verify exposure and assess potential impact, given the remote exploitation possibility and HIGH severity of the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-120238 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-120238

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-120238 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-120238

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.