SECURITYCRITICALCVE-2026-54630

CVE-2026-54630: Part-DB Phar Upload Bypass Enables Code Execution (CVSS 9.6)

Part-DB before 2.12.1 stores attachment uploads in a web-served directory and its extension blocklist omits phar. Upgrade to 2.12.1.

Dylan H.

Security Team

October 23, 2026
2 min read
CVE-2026-54630: Part-DB Phar Upload Bypass Enables Code Execution (CVSS 9.6)

Critical severity

Rated critical. Prioritise patching — see the remediation guidance below.

Affected Products

  • Part-DB versions before 2.12.1

Executive Summary

CVE-2026-54630 affects Part-DB, an open source inventory management system for electronic components. Before version 2.12.1, the part attachment upload handler stores uploaded files under the web-served media directory using the client-supplied file extension. Its extension blocklist does not include phar, so a phar file can be placed in a directory the web server serves.

CVSS Score: 9.6 (Critical)

The NVD entry was published on October 23, 2026. We could not retrieve the full NVD record, so details below come from the published description.


Vulnerability Overview

AttributeValue
CVE IDCVE-2026-54630
CVSS Score9.6 (Critical)
TypeUnrestricted file upload via incomplete blocklist
ComponentPart attachment upload handler
Fixed Version2.12.1

Blocklists of dangerous extensions are fragile: any executable type left off the list becomes a bypass. Because the file keeps the client-supplied extension and lives in a web-served path, an uploaded phar archive can be reached directly over HTTP. Whether it executes depends on how the PHP and web server configuration handles .phar files.


Remediation

  1. Upgrade Part-DB to 2.12.1 or later.
  2. Review the media and attachment directories for files with phar or other unexpected extensions, and remove any you cannot account for.
  3. Restrict who can upload attachments until the upgrade is done.
  4. Configure the web server to deny script execution in upload directories.

References