CVE-2025-12387VulnerabilityPublished 27 Jan 2026

CVE-2025-12387: Pix-Link LV-WR21Q · Unchecked Error Condition

Affects Pix-Link LV-WR21QSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Pix-LinkLV-WR21Q	Affected =V108_108	Fixed in–
Pix-LinkWR21Q	Affected =V108_108	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should implement network-level access controls to restrict access to the router's administrator panel, limiting it to trusted management hosts or VPN connections. Monitoring HTTP POST requests to the admin interface for unusual language parameter values can help detect exploitation attempts. Administrators should document and maintain correct language settings to quickly revert if the admin panel becomes unresponsive. Network segmentation can isolate management interfaces from general user traffic, reducing exposure. Where possible, organizations should consider replacing or upgrading affected devices to models with vendor support and security updates. In the absence of vendor patches, deploying web application firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to block malformed language parameter requests can provide additional protection. Regular backups of router configurations will facilitate recovery if the admin panel is disabled. Finally, organizations should engage with Pix-Link or authorized resellers to seek firmware updates or official guidance.

Description

A vulnerability in the Pix-Link LV-WR21Q router's language module allows remote attackers to trigger a denial of service (DoS) by sending a specially crafted HTTP POST request containing non-existing language parameter. This renders the server unable to serve correct lang.js file, which causes administrator panel to not work, resulting in DoS until the language settings is reverted to a correct value. The Denial of Service affects only the administrator panel and does not affect other router functionalities. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version V108_108 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.

Impact

For European organizations, the primary impact of CVE-2025-12387 is the disruption of administrative access to the Pix-Link LV-WR21Q routers. This denial of service on the admin panel can delay or prevent configuration changes, security updates, or incident response actions, potentially increasing exposure to other threats. Although the router's core networking functions remain unaffected, the inability to manage the device can lead to operational challenges, especially in environments where these routers are used for critical connectivity or network segmentation. Organizations relying on centralized or remote management may find recovery slower if the language settings are inadvertently or maliciously changed. The lack of a patch or vendor response increases the risk window. However, since exploitation does not compromise confidentiality or integrity, the direct risk of data breach or device takeover is low. Still, the administrative disruption could be leveraged as part of a broader attack strategy targeting network infrastructure availability.

Summary

CVE-2025-12387 is a vulnerability classified under CWE-754, indicating an improper check for unusual or exceptional conditions within the Pix-Link LV-WR21Q router's language module. The flaw arises when the router processes HTTP POST requests to the administrator panel containing a language parameter value that does not exist. This malformed request causes the router to fail in serving the lang.js JavaScript file, which is essential for the proper functioning of the admin interface. Consequently, the administrator panel becomes unusable, effectively causing a denial of service (DoS) condition. The vulnerability was confirmed in firmware version V108_108, though other versions have not been tested and may also be vulnerable. Exploitation requires no authentication or user interaction and can be performed remotely over the network, making it accessible to any attacker with network access to the device's admin interface. Despite notification, the vendor has not released patches or detailed information about affected versions. The CVSS 4.0 vector (AV:N/AC:L/AT:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N) indicates network attack vector, low attack complexity, no privileges or user interaction required, and low impact on availability. The vulnerability impacts only the availability of the admin panel, leaving other router functions operational. This limits the scope of the attack but still poses a risk by denying administrators access to device management capabilities.

CWE-754Improper Check for Unusual or Exceptional Conditions (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Check the results of all functions that return a value and verify that the value is expected.
Implementation
If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 12:20 UTC

WeaknessesCWE-754

Technical details

References

Community reviews

Related threats