dbcve.org
ForumwpWordPress extension · Ultimatemember

CVE-2024-54367

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-16
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data vulnerability in Ultimate Member ForumWP forumwp allows Object Injection.This issue affects ForumWP: from n/a through <= 2.1.0.

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 deserialization of untrusted data vulnerability in the ForumWP plugin allows attackers to inject PHP objects via unsafe deserialization, potentially leading to remote code execution. The vulnerability exists in versions up to and including 2.1.0.

MitigationUpgrade to a patched version of ForumWP that properly validates or sanitizes deserialized data, or implement input validation to prevent untrusted data from being deserialized.

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
ForumwpWordPress extension
Affected:< 2.1.1

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
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 checks

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

  1. Confirm ForumWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ForumWP' or 'Ultimatemember Forumwp' in the list. Alternatively, check the /wp-content/plugins/forumwp/ directory exists.
    Affected if ForumWP plugin directory or entry exists in WordPress installation
  2. Identify installed ForumWP version
    Open the main plugin file (forumwp/forumwp.php) and look for the 'Version:' header in the plugin comments, or check the plugin entry in WordPress admin which displays the version number.
    Affected if Version displayed is 2.1.0 or lower (any version below 2.1.1)
  3. Verify deserialization is reachable
    Review plugin code for calls to unserialize() function, particularly those operating on user-supplied input from $_POST, $_GET, $_REQUEST, or database values. Check files in /includes/ directory for unserialize usage.
    Affected if unserialize() calls exist without prior sanitization of input data sources
  4. Check if plugin processes serialized data from external sources
    Examine PHP files handling form submissions, AJAX requests, or database-retrieved settings that may flow into deserialization. Look for $_POST/$_GET parameters being saved and later unserialized.
    Affected if Plugin accepts and later deserializes data from frontend forms, API endpoints, or user-modified database entries

If ForumWP version is 2.1.0 or below and the plugin processes untrusted data through unserialize(), the environment is vulnerable to CVE-2024-54367.

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 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade to a patched version of ForumWP that properly validates or sanitizes deserialized data, or implement input validation to prevent untrusted data from being deserialized.

Recommended fix High confidence

ForumWP version 2.1.1

  1. 1. Create a complete backup of the WordPress site including database and files
  2. 2. Update ForumWP plugin to version 2.1.1 or later via WordPress admin dashboard (Plugins > All Plugins > ForumWP > Update Now)
  3. 3. Alternatively, update via FTP by downloading ForumWP 2.1.1 from the official WordPress repository and replacing the /wp-content/plugins/forumwp/ directory
  4. 4. Verify the update was successful by checking the Plugins page shows ForumWP version 2.1.1 or higher
  5. 5. Test critical site functionality to ensure the update did not break existing features

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

Fix this in Forumwp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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