Media File Renamer – Auto & Manual Rename <= 5.2.5 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 5.2.6
- Affected Plugin
- Media File Renamer: Rename for better SEO (AI-Powered)
- Affected Version
<= 5.2.5- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-36850
At a glance
CVE-2021-36850 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Media File Renamer WordPress plugin, affecting versions <= 5.2.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.2.6; sites on affected versions should update now. Disclosed April 2021, reported by Ngo Van Thien.
Vulnerability Overview
Cross-Site Request Forgery (CSRF) vulnerability in WordPress Media File Renamer – Auto & Manual Rename plugin (versions <= 5.2.5). Affected parameters "post_title", "filename", "lock". This allows changing the uploaded media title, media file name, and media locking state.
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 privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Media File Renamer <= 5.2.5 carries this weakness at post_title, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Media File Renamer the fix is 5.2.6: builds <= 5.2.5 are affected, anything from 5.2.6 onward is not.
Remediation
Update to version 5.2.6, 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 5.2.6 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.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 - 6.4CVE-2014-2040: Media File Renamer < 1.9.4 Stored Cross-Site Scripting
CVE-2014-2040 - 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