CVE-2019-9142: An issue was discovered in b3log Symphony (aka Sym) before v3.4.7

Q: How do I fix CVE-2019-9142?

symphony: upgrade to 3.4.7. Exact commands for each OS are on this page.

Q: Is CVE-2019-9142 being exploited?

CVE-2019-9142 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-9142 affect?

CVE-2019-9142 affects symphony. Severity is medium (CVSS 6.1). 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.

Q: How urgent is CVE-2019-9142?

Priority 36/100. No elevated risk signals yet.

Routine

MEDIUM 6.1UPGRADE

CVE-2019-9142 is a medium-severity flaw (CVSS 6.1) affecting symphony. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-79
Published	2019-02-25
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: b3log

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-02-25 15:29 UTCPublished CVE record published
2026-06-17 02:43 UTCUpdated Record last modified

b3log symphony UPGRADE

Affected: < 3.4.7

Fixed in: 3.4.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy symphony || rpm -q symphony || symphony --version

2. UPGRADE to 3.4.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade symphony

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade symphony

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-9142?

symphony: upgrade to 3.4.7. Exact commands for each OS are on this page.

Is CVE-2019-9142 being exploited?

CVE-2019-9142 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-9142 affect?

CVE-2019-9142 affects symphony. Severity is medium (CVSS 6.1). 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.

How urgent is CVE-2019-9142?

Priority 36/100. No elevated risk signals yet.

Software pages

Java vulnerabilities

Related CVEs

CVE-2020-25912 CRITICAL 9.1 DOWNGRADE A XML External Entity (XXE) vulnerability was discovered in symphony\lib\toolkit\class.xmlelement.php in Symph
CVE-2020-25343 MEDIUM 5.4 DOWNGRADE Cross-site scripting (XSS) vulnerabilities in Symphony CMS 3.0.0 allow remote attackers to inject arbitrary we
CVE-2020-17405 HIGH 8.8 DOWNGRADE This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Se
CVE-2020-15071 MEDIUM 6.1 DOWNGRADE content/content.blueprintsevents.php in Symphony CMS 3.0.0 allows XSS via fields['name'] to appendSubheading.
CVE-2019-17488 MEDIUM 6.1 UPGRADE b3log Symphony (aka Sym) before 3.6.0 has XSS via the HTTP User-Agent header.

References

← Back to latest CVEs