Media File Renamer < 1.9.4 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.9.4
- Affected Plugin
- Media File Renamer: Rename for better SEO (AI-Powered)
- Affected Version
< 1.9.4- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2014-2040
At a glance
CVE-2014-2040 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Media File Renamer WordPress plugin, affecting versions < 1.9.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.9.4; sites on affected versions should update now. Disclosed January 2014, reported by Larry W. Cashdollar.
Vulnerability Overview
Multiple cross-site scripting (XSS) vulnerabilities in the (1) callback_multicheck, (2) callback_radio, and (3) callback_wysiwygin functions in mfrh_class.settings-api.php in the Media File Renamer plugin 1.7.0 for WordPress allow remote authenticated users with permissions to add media or edit media to inject arbitrary web script or HTML via unspecified parameters, as demonstrated by the title of an uploaded file.
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 Media File Renamer < 1.9.4 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 Media File Renamer the fix is 1.9.4: builds < 1.9.4 are affected, anything from 1.9.4 onward is not.
Remediation
Update to version 1.9.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Media File Renamer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Media File Renamer 1.9.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Media File Renamer: Rename for better SEO (AI-Powered)
- 8.8CVE-2021-36850: Media File Renamer – Auto & Manual Rename CSRF
CVE-2021-36850 - 8.8Media File Renamer – Auto & Manual Rename Missing Authorization Checks
- 6.6CVE-2023-50897: Media File Renamer <= 5.7.7 Remote Code Execution
CVE-2023-50897 - 5.3CVE-2023-44991: Media File Renamer <= 5.6.9 Info Exposure
CVE-2023-44991
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C