What is the CVSS score of CVE-2013-5218?

CVE-2013-5218 has a CVSS 2.0 base score of 2.9 (Low). CVSS vector: AV:A/AC:M/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.8%.

Is there a public PoC exploit available for CVE-2013-5218?

Yes, a public proof-of-concept exploit is available for CVE-2013-5218. Prioritise patching immediately. EPSS: 0.8%.

Hotbox Router Firmware CVE-2013-5218

LOW

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

2013-12-30 cve@mitre.org

XSS Hotbox Router Firmware Hotbox Router

2.9

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.9 LOW

AV:A/AC:M/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:A/AC:M/Au:N/C:N/I:P/A:N

Attack Vector

Adjacent

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Dec 30, 2013 - 04:53 cve.org

LOW 2.9

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability on the HOT HOTBOX router with software 2.1.11 allows remote attackers to inject arbitrary web script or HTML via a crafted DHCP Host Name option, which is not properly handled during rendering of the DHCP table in wlanAccess.asp.

AnalysisAI

Cross-site scripting (XSS) vulnerability on the HOT HOTBOX router with software 2.1.11 allows remote attackers to inject arbitrary web script or HTML via a crafted DHCP Host Name option, which is not. Rated low severity (CVSS 2.9). 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. Cross-site scripting (XSS) vulnerability on the HOT HOTBOX router with software 2.1.11 allows remote attackers to inject arbitrary web script or HTML via a crafted DHCP Host Name option, which is not properly handled during rendering of the DHCP table in wlanAccess.asp. Affected products include: Hot Hotbox Router Firmware, Hot Hotbox Router.

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.