CVE Intelligence
Critical Injection exploit reference

CVE-2026-110957 — Wavlink WL-WN530BE2-A Login Processing api.cgi sub_12580 os command injection

A vulnerability has been found in Wavlink WL-WN530BE2-A up to M30BE2_V250604. The affected element is the function sub_12580 of the file api.cgi of the component Login Processing. The manipulation of the argument REMOTE_ADDR leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2026-09-24-841a51c6d5_tclinux.bin is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms: "We confirm the finding, and it has already been addressed. In the current firmware the api=info&client=app handler no longer builds a shell command: the login script is now invoked through an argument vector (execvp) instead of system(), and the client address is length-limited and null-checked."

Published Oct 15, 2026 · Updated Oct 15, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Wavlink
WL-WN530BE2-A
CVSS base
10.0
Critical · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Wavlink WL-WN530BE2-A).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Wavlink WL-WN530BE2-A version M30BE2_V250604 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
10.0 CVSS 4.0 Critical — — VulDB via CVE Program (cve.org) e CISA ADP
9.3 CVSS 4.0 Critical — — cna@vuldb.com via NIST National Vulnerability Database
10.0 CVSS 3.1 Critical 3.9 6.0 cna@vuldb.com via NIST National Vulnerability Database
10.0 CVSS 3.1 Critical — — VulDB via CVE Program (cve.org) e CISA ADP
10.0 CVSS 3.0 Critical — — VulDB via CVE Program (cve.org) e CISA ADP
10.0 CVSS 2.0 High 10.0 10.0 cna@vuldb.com via NIST National Vulnerability Database
10.0 CVSS 2.0 High — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-77 · Command Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Published → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 15, 2026
  • Affected products added · wavlink/wl-wn530be2-a
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 10.0
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Oct 15, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

6 on the record

Elsewhere on this site

Wavlink
every CVE for this vendor
Injection
same class
CWE-77
other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-110957 is "Wavlink WL-WN530BE2-A Login Processing api.cgi sub_12580 os command injection", rated Critical. It affects WL-WN530BE2-A (Wavlink); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 10.0 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.