An issue in symphony v.3.6.3 and before allows a remote attacker to execute arbitrary code via the log4j component.
Product
b3log symphony vulnerabilities
6 published CVES affecting b3log symphony, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 2
- High
- 0
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest b3log symphony CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 1.2%
-
CVE-2019-17488 b3log Symphony (aka Sym) before 3.6.0 has XSS via the HTTP User-Agent header.
PublishedMediumCVSS 6.1 EPSS 0.82%b3log Symphony (aka Sym) before 3.6.0 has XSS via the HTTP User-Agent header.
-
MediumCVSS 4.8 EPSS 0.52%
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 payload when accessing the /member/test/points URI, allowing remote attacks. Any Web script or HTML can be inserted by an admin...
-
MediumCVSS 6.1 EPSS 0.80%
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.
-
CriticalCVSS 9.8 EPSS 2.1%
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.
-
MediumCVSS 5.4 EPSS 0.48%
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 mishandled during display of a client IP address in /admin/user/userid.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.