CVE-2019-9142: XSS Vulnerability in org.b3log:symphony

org.b3log:symphony Updated 02 Oct 2025

Summary

06/03/2019
Yes i
Moderate
6.1

CVE-2019-9142: Moderate severity vulnerability that affects org.b3log:symphony. Affects org.b3log:symphony versions < 3.4.7. Fixed in 3.4.7. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

org.b3log Symphony (aka Sym) is an open-source content management system (CMS) written in Java. It provides a platform for building and managing websites, blogs, and forums. Symphony allows users to create and customize their websites using various themes and plugins. However, a vulnerability has been discovered in Symphony versions prior to v3.4.7 that exposes users to cross-site scripting (XSS) attacks.

Vulnerability Detail

The vulnerability, identified as CVE-2019-9142, originates from the userIntro and userNickname fields in the processor/SettingsProcessor.java file. These fields are not properly sanitized, allowing malicious users to inject arbitrary JavaScript code into the Symphony application. This XSS vulnerability can lead to various security risks, including session hijacking, defacement of web pages, and theft of sensitive user information.

How To Fix

Minimum fixed version

3.4.7

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to Symphony version 3.4.7 is not immediately feasible, a temporary workaround can be implemented by manually sanitizing the userIntro and userNickname fields in the processor/SettingsProcessor.java file. This can be achieved by using a robust HTML sanitization library or implementing custom input validation and filtering mechanisms. It is crucial to thoroughly test the workaround to ensure it effectively mitigates the XSS vulnerability.

Conclusion

The XSS vulnerability in org.b3log Symphony (aka Sym) versions prior to 3.4.7 poses a significant security risk. It is crucial to upgrade to the latest version or apply the recommended workaround to mitigate the vulnerability. For further assistance and support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for org.b3log:symphony →

Share this vulnerability

FAQ

The vulnerability allows attackers to inject malicious JavaScript code into Symphony, potentially leading to unauthorized access, data theft, and website defacement.

While there are no known public exploits at the moment, it is essential to address this vulnerability promptly to prevent potential attacks.

No, only versions prior to 3.4.7 are affected. Upgrading to the latest version will mitigate the vulnerability.

Yes, this vulnerability can be exploited remotely by attackers who can submit malicious input to the userIntro and userNickname fields.

Yes, the CVSS score for this vulnerability is 6.1, indicating a moderate severity level.

How To Fix

Minimum fixed version

3.4.7

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback