Solid Central <= 3.0.0 - Stored Cross-Site Scripting via packages
Strategic Overview
- Status
- Patched in 3.0.1
- Affected Version
< 3.0.1- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Kadence Central WordPress plugin, affecting versions < 3.0.1. It carries a CVSS score of 5.4 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 3.0.1; sites on affected versions should update now. Disclosed November 2023, reported by Robin Wood.
Vulnerability Overview
The Solid Central – Site Management, Backups, Security, and Reporting plugin for WordPress is vulnerable to Stored Cross-Site Scripting via via malicious package names in all versions up to and including 3.0.0 due to insufficient output escaping. This makes it possible for attackers able to compromise the packages retrieved from the iThemes API to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Note that such a compromise is considered highly unlikely.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Kadence Central < 3.0.1 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Kadence Central the fix is 3.0.1: builds < 3.0.1 are affected, anything from 3.0.1 onward is not.
Remediation
Update to version 3.0.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Kadence Central: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Kadence Central 3.0.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Kadence Central – Site Management, Backups, Security, and Reporting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C