dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-7486

HIGH · 8.8 CVSS v3.1 Published 2024-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 MultiPurpose theme for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.2.0 via deserialization of untrusted input through the 'wpeden_post_meta' post meta. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 MultiPurpose WordPress theme before version 1.2.1 is vulnerable to PHP Object Injection through deserialization of untrusted input in the 'wpeden_post_meta' post meta. Authenticated attackers with Contributor-level access or higher can inject arbitrary PHP objects. While no POP chain exists in the theme itself, a suitable POP chain from another installed plugin or theme could enable remote code execution, file deletion, or data exfiltration.

MitigationUpdate the MultiPurpose theme to version 1.2.1 or later. If no update is available, remove the theme entirely and ensure only trusted users have Contributor-level or higher access.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm MultiPurpose theme is installed
    In WordPress admin, go to Appearance > Themes. Look for 'MultiPurpose' theme in the list of installed themes.
    Affected if MultiPurpose theme appears in the themes list and is either active or exists in the wp-content/themes directory.
  2. Determine the installed theme version
    If the MultiPurpose theme is present, open the theme's style.css file (typically at /wp-content/themes/multipurpose/style.css) and look for the 'Version:' declaration in the file header.
    Affected if The version number found is lower than 1.2.1 (e.g., 1.2.0, 1.1.x, 1.0.x).
  3. Check for vulnerable post meta usage
    Query the WordPress database: SELECT * FROM wp_postmeta WHERE meta_key = 'wpeden_post_meta' LIMIT 10; (adjust wp_ prefix if using custom prefix). Review if any posts have this meta key populated with serialized data.
    Affected if Records exist in wp_postmeta with meta_key 'wpeden_post_meta' and non-empty meta_value containing serialized PHP objects.
  4. Identify users with Contributor-level or higher access
    Query the WordPress database: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities'; Review which users have roles containing 'contributor', 'author', 'editor', or 'administrator'.
    Affected if Any user account exists with Contributor, Author, Editor, or Administrator role in the WordPress installation.

If the MultiPurpose theme is installed with a version before 1.2.1 AND the wpeden_post_meta post meta is being used AND any user with Contributor-level or higher access exists, 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the MultiPurpose theme to version 1.2.1 or later. If no update is available, remove the theme entirely and ensure only trusted users have Contributor-level or higher access.

Recommended fix Moderate confidence

Latest version of MultiPurpose theme (version higher than 1.2.0)

  1. 1. Navigate to the WordPress admin dashboard and go to Appearance > Themes
  2. 2. Identify the MultiPurpose theme in your installed themes list
  3. 3. Check if an update is available for the MultiPurpose theme
  4. 4. If an update is available, backup your WordPress site before proceeding
  5. 5. Update the MultiPurpose theme to the latest available version
  6. 6. Verify the update was successful and the site functions normally
  7. 7. If no update is available through WordPress, manually download the latest version from the official WordPress theme repository or the theme developer's website
  8. 8. Replace the theme files via FTP or the WordPress theme uploader
Caveat Theme updates may modify styling or functionality; test in staging environment before production deployment

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

Have this fixed 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 help mitigating

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-7486 — 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-7486 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