WordPress security by component
Media File Renamer
Plugin description
Media File Renamer is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jan 05, 2026; the highest CVE/CNA score is 9.1.
Plugin slug:
media-file-renamerLatest vulnerability
CVE-2023-50897: Media File Renamer: Dangerous file upload
Media File Renamer is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
| Safe version |
|
||
|---|---|---|---|
| Jan 05, 2026 |
CVE-2023-50897
Media File Renamer: Dangerous file upload
Media File Renamer is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
|
See mitigation notes |
CVE9.1
NVDPending
|
| Dec 19, 2023 |
CVE-2023-44991
Media File Renamer: Rename Files (Manual, Auto & AI): A security weakness
Media File Renamer: Rename Files (Manual, Auto & AI) is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.5
NVD7.5
|
| Oct 04, 2021 |
CVE-2021-36850
Media File Renamer: Cross-site request forgery
Media File Renamer is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE5.4
NVD4.3
|
| Mar 03, 2014 |
CVE-2014-2040
Media File Renamer: Cross-site scripting
Media File Renamer is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE2.1
NVD2.1
|