B3log Symphony
6 CVEs affecting B3log Symphony. Latest disclosed: 2024-02-05. Critical: 2, High: 0.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2024-23049 | Critical | 9.8 | 2024-02-05 | An issue in symphony v.3.6.3 and before allows a remote attacker to execute arbitrary code via the log4j component. |
CVE-2018-10469 | Critical | 9.8 | 2018-04-27 | b3log Symphony (aka Sym) 2.6.0 allows remote attackers to upload and execute arbitrary JSP files via the name[] parameter to the /upload URI. |
CVE-2019-17488 | Medium | 6.1 | 2019-10-10 | b3log Symphony (aka Sym) before 3.6.0 has XSS via the HTTP User-Agent header. |
CVE-2019-9142 | Medium | 6.1 | 2019-02-25 | An issue was discovered in b3log Symphony (aka Sym) before v3.4.7. XSS exists via the userIntro and userNickname fields to processor/SettingsProcessor.java. |
CVE-2017-16821 | Medium | 5.4 | 2017-11-15 | b3log Symphony (aka Sym) 2.2.0 has XSS in processor/AdminProcessor.java in the admin console, as demonstrated by a crafted X-Forwarded-For HTTP header that is… |
CVE-2018-16249 | Medium | 4.8 | 2019-06-20 | In Symphony before 3.3.0, there is XSS in the Title under Post. The ID "articleTitle" of this is stored in the "articleTitle" JSON field, and executes a payloa… |