dbcve.org
Post Meta Data ManagerWordPress extension · Wpexpertplugins

CVE-2024-13835

HIGH · 7.2 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to after 1.4.3 or later.
See remediation →
78/100
Remediation priority · High
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 Post Meta Data Manager plugin for WordPress is vulnerable to multisite privilege escalation in all versions up to, and including, 1.4.4. This is due to the plugin not properly verifying the existence of a multisite installation prior to allowing user meta to be added/modified. This makes it possible for authenticated attackers, with Administrator-level access and above, to gain elevated privileges on subsites that would otherwise be inaccessible.

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 Post Meta Data Manager WordPress plugin versions up to 1.4.4 lacks proper validation of multisite installation status before permitting user meta add/modify operations. This allows a subsite Administrator to manipulate user meta data in ways that escalate privileges across the multisite network, bypassing subsite isolation controls.

MitigationUpdate the Post Meta Data Manager plugin to version 1.4.5 or later which properly checks for multisite installation before allowing user meta modifications.

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
Post Meta Data ManagerWordPress extension
Affected:<= 1.4.3

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

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Check if Post Meta Data Manager plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Post Meta Data Manager' by wpexpertplugins in the list.
    Affected if Plugin is not found in the installed plugins list
  2. Verify the installed plugin version
    In the Plugins list, locate Post Meta Data Manager and check the version number displayed below the plugin name. Compare it to the affected range <= 1.4.3.
    Affected if Version number is 1.4.3 or lower
  3. Confirm WordPress multisite installation
    Check if the WordPress site is running in multisite mode by looking for 'Network Admin' in the admin menu bar, or by inspecting wp-config.php for 'MULTISITE' constant set to true.
    Affected if Site is NOT a multisite installation (the vulnerability requires multisite to be exploitable)
  4. Verify subsite Administrator access to plugin functionality
    Log in as an Administrator on a subsite (not the network admin) and attempt to access the Post Meta Data Manager plugin features to add or modify user meta data.
    Affected if Subsite Administrator can access user meta add/modify operations (indicates isolation controls may be bypassed)

A user is affected if the Post Meta Data Manager plugin version is 1.4.3 or lower, the WordPress installation is multisite, and a subsite Administrator can access user meta modification features without proper network-level validation.

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

Update the Post Meta Data Manager plugin to version 1.4.5 or later which properly checks for multisite installation before allowing user meta modifications.

Recommended fix Moderate confidence

Latest version of Post Meta Data Manager (check WordPress plugin repository for current release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Post Meta Data Manager' in the plugin list
  4. Check the current installed version displayed below the plugin name
  5. If the installed version is 1.4.4 or below, click 'Update Now' to upgrade to the latest version
  6. Alternatively, navigate to Dashboard > Updates and check for available updates
  7. After updating, verify the new version number to confirm the upgrade was successful

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

Fix this in Post Meta Data Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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