VYPR
Unrated severityNVD Advisory· Published Mar 1, 2022· Updated Aug 4, 2024

CVE-2021-46387

CVE-2021-46387

Description

ZyXEL ZyWALL 2 Plus is vulnerable to reflected XSS via insecure URI handling, allowing arbitrary JavaScript execution and session hijacking.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

ZyXEL ZyWALL 2 Plus is vulnerable to reflected XSS via insecure URI handling, allowing arbitrary JavaScript execution and session hijacking.

Vulnerability

ZyXEL ZyWALL 2 Plus Internet Security Appliance is affected by a Cross-Site Scripting (XSS) vulnerability due to insecure URI handling. The vulnerability allows bypassing security restrictions, enabling an attacker to inject arbitrary JavaScript. Affected versions are not explicitly listed in the available references, but the device itself is the subject of the advisory [1][2].

Exploitation

An attacker must trick an authenticated user into clicking a crafted link that contains malicious JavaScript in the URI. No other authentication or network position is required beyond the ability to deliver the link to a user who is logged into the appliance's management interface [1].

Impact

Successful exploitation enables the attacker to execute arbitrary JavaScript in the context of the victim's session, leading to clipboard hijacking and session hijacking [1]. The attacker can potentially perform any action available to the victim, including configuration changes or data exfiltration.

Mitigation

As of the publication date (2022-03-01), no fixed version is mentioned in the available references [1][2]. Users are advised to monitor vendor advisories for a patch and to restrict access to the management interface as a workaround.

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.