What is the CVSS score of CVE-2024-51189?

CVE-2024-51189 has a CVSS 3.1 base score of 4.8 (Medium). CVSS vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.4%.

Is there a public PoC exploit available for CVE-2024-51189?

Yes, a public proof-of-concept exploit is available for CVE-2024-51189. Prioritise patching immediately. EPSS: 0.4%.

Tew 651Br Firmware CVE-2024-51189

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2024-11-11 cve@mitre.org

XSS Tew 651Br Firmware Tew 652Brp Firmware Tew 652Bru Firmware

4.8

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

4.8 MEDIUM

AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Primary rating from Vendor (mitre) · only source for this CVE.

CVSS VectorVendor: mitre

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Nov 11, 2024 - 20:15 cve.org

MEDIUM 4.8

DescriptionCVE.org

AnalysisAI

TRENDnet TEW-651BR 2.04B1, TEW-652BRP 3.04b01, and TEW-652BRU 1.00b12 devices contain a Store Cross-site scripting (XSS) vulnerability via the macList_Name_1.1.1.0.0 parameter on the /filters.htm. Rated medium severity (CVSS 4.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. TRENDnet TEW-651BR 2.04B1, TEW-652BRP 3.04b01, and TEW-652BRU 1.00b12 devices contain a Store Cross-site scripting (XSS) vulnerability via the macList_Name_1.1.1.0.0 parameter on the /filters.htm page. Affected products include: Trendnet Tew-651Br Firmware, Trendnet Tew-652Brp Firmware, Trendnet Tew-652Bru Firmware.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.