CVE-2015-4661 json
Cross-site scripting (XSS) vulnerability in Symphony CMS 2.6.2 allows remote attackers to inject arbitrary web script or HTML via the sort…
published 11y ago modified 4mo ago also EUVD-2015-4680
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in Symphony CMS 2.6.2 allows remote attackers to inject arbitrary web script or HTML via the sort parameter to system/authors.
Is CVE-2015-4661 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
2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/archive/1/535714/100/0/threaded referenced PoC, tagged "exploit" by a source, unverified
- hyp3rlinx.altervista.org http://hyp3rlinx.altervista.org/advisories/AS-SYMPHONY0606.txt referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/132193/Symphony-CMS-2.6.2-Cross-Site-Scripting.html 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
-
securityfocus.com
/archive/1/535714/100/0/threaded
mailing-list, exploit, third-party-advisory, vdb-entry
-
hyp3rlinx.altervista.org
/advisories/AS-SYMPHONY0606.txt
exploit, third-party-advisory
-
packetstormsecurity.com
/files/132193/Symphony-CMS-2.6.2-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/75059
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2015-4661
- NVD CVE-2015-4661
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.