dbcve.org
Media ManagerWordPress extension · Userproplugin

CVE-2024-12821

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to after 3.12.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The Media Manager for UserPro plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the upm_upload_media() function in all versions up to, and including, 3.12.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 · high confidence

The Media Manager for UserPro WordPress plugin has a broken access control vulnerability in the upm_upload_media() function. Authenticated users with Subscriber-level access can call this function without proper capability verification, allowing them to update arbitrary WordPress options. Attackers can modify the default_user_role option to Administrator and enable user_registration, then register an admin account.

MitigationAdd proper capability checks (e.g., current_user_can('manage_options')) to the upm_upload_media() function and validate all user inputs before updating options. Update to version 3.12.1 or later if available.

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 ManagerWordPress extension
Affected:<= 3.12.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Confirm UserPro Media Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'UserProplugin Media Manager' or check the plugin files in /wp-content/plugins/ for a media-manager or userpro-related folder. Check the main plugin file header for the Version: X.X.X field.
    Affected if The installed version is 3.12.0 or lower, or if the version cannot be determined and the plugin is present.
  2. Verify the upm_upload_media function exists
    Search the plugin directory (via FTP or file manager) for the file containing 'function upm_upload_media'. Examine the function code to see if it performs any capability checks before updating options.
    Affected if The function exists and lacks a capability check like current_user_can('manage_options') before processing option updates.
  3. Check if AJAX actions are exposed without authentication barriers
    Search plugin files for 'add_action' or 'add_shortcode' registrations of 'upm_upload_media' or related AJAX endpoints. Look at wp-admin/admin-ajax.php?action=upm_... to see if the action is registered without a capability verification hook.
    Affected if The AJAX action is publicly accessible or accessible to Subscriber-level users without proper permission verification.
  4. Inspect WordPress options that could be modified
    Query the wp_options table (via phpMyAdmin or WP CLI: wp db query "SELECT * FROM wp_options WHERE option_name IN ('default_user_role', 'users_can_register', 'default_role')") to see current values.
    Affected if default_user_role is set to 'administrator' or 'editor', users_can_register is enabled, or default_role allows admin-level access when the plugin's upload function is reachable by low-privilege users.

You are affected if the UserPro Media Manager plugin version is 3.12.0 or lower AND the upm_upload_media function is accessible to Subscriber-level users without capability checks, allowing them to modify WordPress user registration options.

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 3.12.0
Interim mitigation

Add proper capability checks (e.g., current_user_can('manage_options')) to the upm_upload_media() function and validate all user inputs before updating options. Update to version 3.12.1 or later if available.

Recommended fix Moderate confidence

Latest version available from vendor (version higher than 3.12.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Media Manager for UserPro plugin
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the vendor (codecanyon.net) and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the site still functions correctly

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

Fix this in Media Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12821 — 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-2024-12821 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