CVE-2013-5300 json
Multiple cross-site scripting (XSS) vulnerabilities in AlienVault Open Source Security Information Management (OSSIM) before 4.3.0 allow re…
published 13y ago modified 4mo ago also EUVD-2013-5140
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in AlienVault Open Source Security Information Management (OSSIM) before 4.3.0 allow remote attackers to inject arbitrary web script or HTML via the withoutmenu parameter to (1) vulnmeter/index.php or (2) vulnmeter/sched.php; the (3) section parameter to av_inventory/task_edit.php; the (4) profile parameter to nfsen/rrdgraph.php; or the (5) scan_server or (6) targets parameter to vulnmeter/simulate.php.
Is CVE-2013-5300 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 FencerExploit prediction
1.78% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
secunia.com
/advisories/54264
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/54287
third-party-advisory, vendor-advisory
-
osvdb.org
/show/osvdb/95814
vdb-entry
-
osvdb.org
/show/osvdb/95818
vdb-entry
-
osvdb.org
/show/osvdb/95816
vdb-entry
- packetstormsecurity.com /files/122547/Alienvault-OSSIM-Cross-Site-Scripting.html
-
securityfocus.com
/bid/61456
vdb-entry
-
osvdb.org
/show/osvdb/95813
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/85994
vdb-entry
- forums.alienvault.com /discussion/1609/patch-release-4-3-1
-
osvdb.org
/show/osvdb/95817
vdb-entry
Sources
- CVE List CVE-2013-5300
- NVD CVE-2013-5300
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.