VYPR
Unrated severityNVD Advisory· Published Oct 15, 2024· Updated Oct 15, 2024

NewType WebEIP v3.0 - Reflected XSS

CVE-2024-9969

Description

NewType WebEIP v3.0 is vulnerable to reflected XSS via improper input validation, allowing JavaScript injection by authenticated attackers.

AI Insight

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

NewType WebEIP v3.0 is vulnerable to reflected XSS via improper input validation, allowing JavaScript injection by authenticated attackers.

Vulnerability

NewType WebEIP v3.0 does not properly validate user input in specific parameters, allowing a remote attacker with regular privileges to insert arbitrary JavaScript. This reflected Cross-site Scripting (XSS) vulnerability affects WebEIP v3.0, which has been unsupported for over 15 years [1][2].

Exploitation

An attacker must have a valid account with regular privileges. By crafting a malicious URL with injected JavaScript code in specific parameters, the attacker can trick a victim into clicking the link, causing the script to execute in the victim's browser context [1][2].

Impact

Successful exploitation enables the attacker to execute arbitrary JavaScript in the victim's browser, leading to potential disclosure of session cookies, redirection to malicious sites, or defacement of the web interface. The CVSS v3.1 score is 5.4 (Medium) with vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, indicating low confidentiality and integrity impact with scope change [1][2].

Mitigation

The vendor has confirmed that WebEIP v3.0 is no longer maintained. No security patch will be released. Users are strongly advised to upgrade to the new WebEIP Pro product [1][2].

AI Insight generated on May 26, 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

2

News mentions

0

No linked articles in our index yet.