CVE-2014-6070 json
Multiple cross-site scripting (XSS) vulnerabilities in Adiscon LogAnalyzer before 3.6.6 allow remote attackers to inject arbitrary web scri…
published 12y ago modified 4mo ago also EUVD-2014-5957
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site scripting (XSS) vulnerabilities in Adiscon LogAnalyzer before 3.6.6 allow remote attackers to inject arbitrary web script or HTML via the hostname in (1) index.php or (2) detail.php.
Patch / fix
Is CVE-2014-6070 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-34525)
- Published
Exploit prediction
3.58% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34525 Syslog LogAnalyzer 3.6.5 - Persistent Cross-Site Scripting webapps, 2014-09-02
- packetstormsecurity.com http://packetstormsecurity.com/files/128121/LogAnalyzer-3.6.5-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2014/Sep/17 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
loganalyzer.adiscon.com
/downloads/loganalyzer-3-6-6-v3-stable
patch
-
exploit-db.com
/exploits/34525
exploit
-
packetstormsecurity.com
/files/128121/LogAnalyzer-3.6.5-Cross-Site-Scripting.html
exploit
-
seclists.org
/fulldisclosure/2014/Sep/17
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95677
vdb-entry
Sources
- CVE List CVE-2014-6070
- NVD CVE-2014-6070
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.