dbcve.org
PmbApplication · Sigb

CVE-2024-26289

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-27
Fix available
A fix is available. Upgrade to 7.3.18 / 7.4.9 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 PMB Services PMB allows Remote Code Inclusion.This issue affects PMB: from 7.5.1 before 7.5.6-2, from 7.4.1 before 7.4.9, from 7.3.1 before 7.3.18.

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

A deserialization of untrusted data vulnerability in PMB Services PMB allows attackers to achieve remote code execution by injecting malicious serialized objects. This stems from insecure deserialization of user-supplied data without proper validation, enabling remote code inclusion.

MitigationUpgrade PMB to version 7.5.6-2, 7.4.9, or 7.3.18 or later. If immediate patching is not possible, implement strict input validation and disable unsafe deserialization features.

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
PmbApplication
Affected:>= 7.3.1, < 7.3.18>= 7.4.1, < 7.4.9>= 7.5.1, < 7.5.6-2

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. Identify installed PMB version
    Locate the PMB version file or check the administration interface for the current version number. Common locations include a version.php file or the 'About' section in admin panel.
    Affected if The installed version falls within 7.3.1 to 7.3.17, 7.4.1 to 7.4.8, or 7.5.1 to 7.5.6-1
  2. Determine if PMB Services component is in use
    Identify whether the PMB Services module or endpoint is enabled and accessible in the installation. Review enabled modules or services configuration.
    Affected if PMB Services is installed and accessible
  3. Identify deserialization entry points
    Review application endpoints or functions that accept and deserialize user-supplied data. Look for code paths that use PHP unserialize() on input from external sources.
    Affected if User-supplied data is being deserialized without validation
  4. Check input validation on serialization endpoints
    Inspect the code handling serialized data input for proper sanitization, type checking, or use of safe deserialization methods.
    Affected if No validation is performed on deserialized data before use

You are affected if your PMB version is within 7.3.1 to 7.3.17, 7.4.1 to 7.4.8, or 7.5.1 to 7.5.6-1 AND your installation deserializes user-supplied data without 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 7.3.18 / 7.4.9 / 7.5.6-2 or later
Fixed in 7.3.187.4.97.5.6-2
Interim mitigation

Upgrade PMB to version 7.5.6-2, 7.4.9, or 7.3.18 or later. If immediate patching is not possible, implement strict input validation and disable unsafe deserialization features.

Recommended fix High confidence

PMB 7.3.18, 7.4.9, or 7.5.6-2 (depending on your current major version branch)

  1. 1. Backup the current PMB installation and database before proceeding with any upgrade
  2. 2. Download the appropriate fixed version from the official PMB source (forge.sigb.net or github.com)
  3. 3. For versions 7.3.x: upgrade to 7.3.18; for versions 7.4.x: upgrade to 7.4.9; for versions 7.5.x: upgrade to 7.5.6-2
  4. 4. Extract the new version files to replace the existing PMB installation
  5. 5. Update the PMB configuration files if required by comparing old and new config structures
  6. 6. Run any database migration scripts included in the new version
  7. 7. Verify the upgrade by logging into the PMB admin interface
  8. 8. Test critical functionality to ensure the upgrade was successful
Caveat Review release notes for any breaking changes between your current version and the target upgrade version before proceeding

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

Fix this in Pmb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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