dbcve.org
Media File Renamer Auto \& Manual RenameWordPress extension · Meowapps

CVE-2023-44991

HIGH · 7.5 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to after 5.6.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Jordy Meow Media File Renamer: Rename Files (Manual, Auto & AI).This issue affects Media File Renamer: Rename Files (Manual, Auto & AI): from n/a through 5.6.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A sensitive information disclosure vulnerability in the Jordy Meow Media File Renamer WordPress plugin allows unauthorized actors to access sensitive data. The specific nature of the exposed information is not detailed in available references.

MitigationUpdate to the latest version of the Media File Renamer plugin once a patched release is available, as version 5.6.9 and prior versions are affected. Review access controls and ensure proper authorization checks are in place.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Media File Renamer Auto \& Manual RenameWordPress extension
Affected:<= 5.6.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Media File Renamer plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/media-file-renamer/ directory via file system
    Affected if The Media File Renamer plugin (by Meowapps) appears in the installed plugins list
  2. Determine installed plugin version
    In WordPress admin, click on the plugin name in the plugins list to view version details, or read the main plugin PHP file header for the Version field
    Affected if The installed version number is 5.6.9 or lower (any version <= 5.6.9)
  3. Check if rename functionality is accessible without authentication
    Attempt to access Media File Renamer AJAX endpoints or admin pages while logged out (e.g., /wp-admin/admin-ajax.php?action=mfrh_... or direct access to Media > File Renamer menu)
    Affected if The plugin functions or pages load and allow interaction without requiring WordPress login authentication
  4. Inspect plugin settings for authorization controls
    Navigate to Media > File Renamer in WordPress admin and review the plugin settings page for any access control, role restrictions, or API configuration options
    Affected if Settings allow broad access or there are no visible role/authorization restrictions configured

If Media File Renamer plugin version 5.6.9 or lower is installed AND the plugin functionality is accessible without proper authentication, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.6.9
Interim mitigation

Update to the latest version of the Media File Renamer plugin once a patched release is available, as version 5.6.9 and prior versions are affected. Review access controls and ensure proper authorization checks are in place.

Recommended fix Moderate confidence

Version greater than 5.6.9 (check WordPress plugin repository for latest stable release)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to your WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Media File Renamer: Rename Files (Manual, Auto & AI)'
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the plugin updated successfully to a version higher than 5.6.9
  7. 7. Test the plugin functionality to ensure it works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Media File Renamer Auto \& Manual Rename Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-44991 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data