dbcve.org
PmbApplication · Sigb

CVE-2025-48744

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-27
Fix available
A fix is available. Upgrade to 8.0.1.2 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
In SIGB PMB before 8.0.1.2, attackers can achieve Local File Inclusion and remote code execution.

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

SIGB PMB before version 8.0.1.2 contains a Local File Inclusion (LFI) vulnerability that allows attackers to read sensitive files from the server filesystem, which can be escalated to achieve Remote Code Execution (RCE).

MitigationUpgrade SIGB PMB to version 8.0.1.2 or later to patch the LFI vulnerability. If immediate patching is not possible, restrict web server access and disable any unnecessary file inclusion functionality.

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:< 8.0.1.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 SIGB PMB version
    Locate the version file or admin panel in the SIGB PMB installation directory, or query the application for its version information (often visible in footer, about page, or version-specific config file)
    Affected if The installed version is lower than 8.0.1.2 (e.g., 8.0.0, 7.x, or earlier releases)
  2. Verify application is network-accessible
    Confirm the SIGB PMB web interface is reachable over HTTP/HTTPS from an untrusted network (e.g., external IP, DMZ deployment)
    Affected if The application is exposed to the internet or untrusted internal networks without authentication barriers
  3. Check for unauthenticated access to vulnerable endpoints
    Attempt to access common SIGB PMB endpoints without credentials to confirm the LFI vector is reachable
    Affected if Unauthenticated users can directly access file-inclusion-prone parameters in the application (the specific endpoint is not detailed in this CVE data)
  4. Review web server access logs for LFI indicators
    Search server logs for suspicious patterns such as ../, ..\, /etc/passwd, or other file path traversal attempts targeting the SIGB PMB application
    Affected if Log entries show traversal attempts (e.g., ../../etc/passwd) from external sources within a timeframe corresponding to this CVE disclosure

If SIGB PMB version is below 8.0.1.2 and the web interface is accessible without authentication, the environment is likely affected by this LFI 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
Upgrade available Upgrade to 8.0.1.2 or later
Fixed in 8.0.1.2
Interim mitigation

Upgrade SIGB PMB to version 8.0.1.2 or later to patch the LFI vulnerability. If immediate patching is not possible, restrict web server access and disable any unnecessary file inclusion functionality.

Recommended fix Moderate confidence

8.0.1.2

  1. 1. Backup the current PMB installation and database before proceeding with any upgrade.
  2. 2. Download PMB version 8.0.1.2 or later from the official SIGB PMB distribution channels (forge.sigb.net or www.sigb.net).
  3. 3. Replace the existing PMB installation files with the new version, preserving custom configurations and the database connection settings.
  4. 4. Verify file permissions are correctly set after the upgrade.
  5. 5. Test the application to ensure normal functionality after the upgrade.
  6. 6. Confirm the path traversal vulnerability is resolved by verifying the fix is applied.
Caveat Review PMB 8.0.1.2 release notes for any configuration or compatibility changes before upgrading.

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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