Media File Renamer – Auto & Manual Rename <= 5.2.5 - Missing Authorization Checks

2012-09-03 00:00
Anonymous

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-862 · Missing Authorization
CVE
CVE pending
View all Media File Renamer: Rename for better SEO (AI-Powered) vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization 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). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.2.6; sites on affected versions should update now. Disclosed September 2012.

Vulnerability Overview

The Media File Renamer – Auto & Manual Rename plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the 'get_license' and 'set_license' API endpoints in versions up to, and including, 5.2.5. This makes it possible for authenticated Subscriber+ attackers to bypass otherwise restricted security protocols.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Media File Renamer <= 5.2.5 carries this weakness at get_license, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. 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.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/beb47081-ad9c-4ecb-bbcd-2ae916e55baf

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C