My Content Management <= 1.7.1 - Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.7.2
- Affected Plugin
- My Content Management
- Affected Version
1.7.1- CVSS
- 6.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 My Content Management WordPress plugin, affecting versions 1.7.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.7.2; sites on affected versions should update now. Disclosed June 2022.
Vulnerability Overview
The My Content Management plugin for WordPress may have been vulnerable to Cross-Site Scripting in versions less than or equal to 1.7.1. Version 1.7.2 of the plugin implemented extensive sanitization and escaping on user supplied inputs which means there may have been exploitable cross-site scripting vulnerabilities present in versions older than 1.7.2.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in My Content Management 1.7.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 My Content Management the fix is 1.7.2: builds 1.7.1 are affected, anything from 1.7.2 onward is not.
Remediation
Update to version 1.7.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to My Content Management: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: My Content Management 1.7.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C