Media ManagerWordPress extension · Userproplugin
CVE-2024-12822
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 · uneditedThe 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 add_capto_img() function in all versions up to, and including, 3.11.0. This makes it possible for unauthenticated attackers 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 confidenceThe Media Manager for UserPro plugin for WordPress contains a missing capability check in the add_capto_img() function (versions up to 3.11.0), allowing unauthenticated attackers to modify arbitrary WordPress options. Attackers can enable user registration and set the default new user role to Administrator, then register an admin account to fully compromise the site.
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
<= 3.11.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check UserPro plugin versionAccess WordPress admin dashboard, navigate to Plugins section, locate UserPro plugin, and verify the installed version number. Alternatively, check the plugin's main PHP file (typically /wp-content/plugins/userpro/functions.php or similar) for the version definition.Affected if The installed version is 3.11.0 or lower, indicating the vulnerable version range.
-
Confirm Media Manager component is activeNavigate to WordPress admin > UserPro > Media Manager settings, or check the plugins list for the Media Manager module being enabled. This component contains the vulnerable add_capto_img() function.Affected if Media Manager is installed and active, exposing the vulnerable function.
-
Verify WordPress user registration settingGo to WordPress admin dashboard > Settings > General > 'Membership' section, and check if 'Anyone can register' is enabled.Affected if User registration is enabled, which is required for the attack chain to work (attacker enables this if not already set).
-
Inspect for unauthorized admin accountsNavigate to WordPress admin > Users > All Users and review the list of users with Administrator role. Look for unfamiliar admin accounts that were not created by legitimate administrators.Affected if Unexpected or unknown admin accounts exist, indicating the exploit may have been used to compromise the site.
The environment is affected if UserPro plugin version 3.11.0 or lower is installed with Media Manager active, regardless of current registration settings, as the vulnerability allows unauthenticated attackers to enable registration and create admin accounts.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to version 3.12.0 or later which includes proper capability checks. If immediate upgrade is not possible, disable user registration or restrict the plugin's functionality until the patch can be applied.
Fix this in Media Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12822 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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