dbcve.org
Mambo Joomla ImporterWordPress extension · Misterpah

CVE-2024-13899

HIGH · 7.2 CVSS v3.1 Published 2025-02-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Mambo Importer plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0 via deserialization of untrusted input via the $data parameter in the fImportMenu function. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 Mambo Importer WordPress plugin is vulnerable to PHP Object Injection in all versions up to 1.0. The vulnerability exists in the fImportMenu function which deserializes untrusted input via the $data parameter. Authenticated administrators can inject PHP objects, but exploitation requires a POP chain from another plugin or theme to achieve impact (file deletion, data retrieval, code execution).

MitigationUpdate Mambo Importer to version 1.1 or later. Remove unused plugins to reduce POP chain availability. Since administrator access is required, audit user accounts and enforce least-privilege principles.

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
Mambo Joomla ImporterWordPress extension
Affected:= 1.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
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. Verify Mambo Importer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Mambo Joomla Importer' or 'Misterpah'. Alternatively, check for the plugin directory at /wp-content/plugins/mambo-importer/
    Affected if The plugin is installed and active
  2. Confirm installed version
    In WordPress admin plugins list, look for the version number under the plugin name. Alternatively, check the main plugin file header at /wp-content/plugins/mambo-importer/mambo-importer.php for the 'Version' field
    Affected if Version is 1.0 or any version below 1.1
  3. Verify administrator user access exists
    Check WordPress user roles at Users > All Users. Confirm if any user has Administrator role. In a compromised scenario, an attacker would need this level of access
    Affected if At least one user with Administrator role exists on the site
  4. Assess POP chain availability
    Review installed plugins and themes for known PHP object injection POP chain gadgets. Common sources include plugins with unserialize() calls on user input, vulnerable serialization handling, or magic methods (__destruct, __wakeup, __invoke) in popular plugins/themes
    Affected if Other vulnerable plugins/themes exist that could provide a POP chain for code execution or file operations

You are affected if the Mambo Importer plugin version 1.0 is installed, you have administrator accounts on the site, and a POP chain gadget exists in another plugin or theme to weaponize the deserialization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Mambo Importer to version 1.1 or later. Remove unused plugins to reduce POP chain availability. Since administrator access is required, audit user accounts and enforce least-privilege principles.

Fix this in Mambo Joomla Importer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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