What is the CVSS score of CVE-2014-0331?

CVE-2014-0331 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.4%.

Is there a public PoC exploit available for CVE-2014-0331?

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

Fortiadc Firmware CVE-2014-0331

MEDIUM

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

2014-04-10 cret@cert.org

XSS Fortiadc Firmware Fortiadc 1000E Fortiadc 1500D Fortiadc 2000D Fortiadc 200D Fortiadc 300E Fortiadc 4000D Fortiadc 400E Fortiadc 600E

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Apr 10, 2014 - 20:29 cve.org

MEDIUM 4.3

DescriptionCVE.org

AnalysisAI

Cross-site scripting (XSS) vulnerability in the web administration interface in FortiADC with firmware before 3.2.1 allows remote attackers to inject arbitrary web script or HTML via the locale. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable. 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 in the web administration interface in FortiADC with firmware before 3.2.1 allows remote attackers to inject arbitrary web script or HTML via the locale parameter to gui_partA/. Affected products include: Fortinet Fortiadc Firmware, Fortinet Fortiadc-1000E, Fortinet Fortiadc-1500D, Fortinet Fortiadc-2000D, Fortinet Fortiadc-200D. Version information: before 3.2.1.

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.