Symphony Project maintains a focused, niche communication and collaboration platform where its vulnerability footprint concentrates in web-facing input-handling defenses, with the durable signal centered on cross-site scripting weaknesses in the Symphony application. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Symphony Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-16956MEDIUM b3log Symphony (aka Sym) 2.2.0 allows an XSS attack by sending a private letter with a certain /article URI, and a second private letter with a modified title. | Nov 27, 2017 | 6.1 | 21 | NO | NO |
CVE-2017-16881MEDIUM b3log Symphony (aka Sym) 2.2.0 does not properly address XSS in JSON objects, as demonstrated by a crafted userAvatarURL value to /settings/avatar, related to processor/AdminProces | Nov 18, 2017 | 6.1 | 18 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Symphony Project.
Media articles that mention a CVE ID that affects a product developed by Symphony Project — matched by CVE ID, not by vendor name.