Part-DB: Authenticated RCE via .phar attachment upload served from public/media
Part-DB is an open source inventory management system for electronic components. Prior to version 2.12.1, the part attachment upload handler stores uploaded files under the web-served media directory using the client-supplied file extension, and its extension blocklist does not include phar. AttachmentSubmitHandler::renameBlacklistedExtensions() rewrites dangerous extensions (php, phtml, sh, cgi, py, js, html, htaccess, ...) to .txt, but phar is absent from the list, so a .phar file keeps its extension. Public attachments (the default) are written into public/media/, which is the Apache document root. The shipped Apache configuration routes .phar to PHP-FPM, so the stored file is executed as PHP on request. The per-attachment-type extension filter is empty by default and is not consulted by the upload handler in a way that blocks this, and a non-admin user in the default users group can create an attachment type with no filter and attach files to parts. Any authenticated user in the default users group uploads a .phar attachment to a part and fetches it under /media/, executing arbitrary PHP as the www-data web user. Ability to exploit depends on the webserver config, docker image contained the vulnerability by default. This issue has been patched in version 2.12.1.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-54630
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 14:23 UTC · Revision 1
Source evidence
Part-DB: Authenticated RCE via .phar attachment upload served from public/media
core-osv · Original sourcePublished 23 Oct 2026, 03:48 UTC
Part-DB is an open source inventory management system for electronic components. Prior to version 2.12.1, the part attachment upload handler stores uploaded files under the web-served media directory using the client-supplied file extension, and its extension blocklist does not include phar. AttachmentSubmitHandler::renameBlacklistedExtensions() rewrites dangerous extensions (php, phtml, sh, cgi, py, js, html, htaccess, ...) to .txt, but phar is absent from the list, so a .phar file keeps its extension. Public attachments (the default) are written into public/media/, which is the Apache document root. The shipped Apache configuration routes .phar to PHP-FPM, so the stored file is executed as PHP on request. The per-attachment-type extension filter is empty by default and is not consulted by the upload handler in a way that blocks this, and a non-admin user in the default users group can create an attachment type with no filter and attach files to parts. Any authenticated user in the default users group uploads a .phar attachment to a part and fetches it under /media/, executing arbitrary PHP as the www-data web user. Ability to exploit depends on the webserver config, docker image contained the vulnerability by default. This issue has been patched in version 2.12.1.
osv:CVE-2026-54630
Complete source record
{
"id": "d10580d73d16fa44f607c6c4bdba1305283d954339d7abc98dd9882823eed727",
"url": "https://osv.dev/vulnerability/CVE-2026-54630",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Part-DB: Authenticated RCE via .phar attachment upload served from public/media",
"summary": "Part-DB is an open source inventory management system for electronic components. Prior to version 2.12.1, the part attachment upload handler stores uploaded files under the web-served media directory using the client-supplied file extension, and its extension blocklist does not include phar. AttachmentSubmitHandler::renameBlacklistedExtensions() rewrites dangerous extensions (php, phtml, sh, cgi, py, js, html, htaccess, ...) to .txt, but phar is absent from the list, so a .phar file keeps its extension. Public attachments (the default) are written into public/media/, which is the Apache document root. The shipped Apache configuration routes .phar to PHP-FPM, so the stored file is executed as PHP on request. The per-attachment-type extension filter is empty by default and is not consulted by the upload handler in a way that blocks this, and a non-admin user in the default users group can create an attachment type with no filter and attach files to parts. Any authenticated user in the default users group uploads a .phar attachment to a part and fetches it under /media/, executing arbitrary PHP as the www-data web user. Ability to exploit depends on the webserver config, docker image contained the vulnerability by default. This issue has been patched in version 2.12.1.",
"evidence": "osv:CVE-2026-54630",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-54630",
"aliases": [
"CVE-2026-54630",
"GHSA-w5m7-3xf7-6g7g"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/part-db/part-db-server",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "57a0dfdbdbb5f26c4f626c0083ec637532236726"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2.12.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "57a0dfdbdbb5f26c4f626c0083ec637532236726"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v2.12.1"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2.12.1"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v2.12.0",
"v2.11.1",
"v2.11.0",
"v2.10.0",
"v2.9.1",
"v2.9.0",
"v2.8.1",
"v2.8.0",
"v2.7.1",
"v2.7.0",
"v2.6.0",
"v2.5.1",
"v2.5.0",
"v2.4.0",
"v2.3.0",
"v2.2.1",
"v2.2.0",
"v2.1.2",
"v2.1.0",
"v2.1.1",
"v2.0.2",
"v2.0.1",
"v2.0.0",
"v1.17.4",
"v1.17.3",
"v1.17.2",
"v1.17.1",
"v1.17.0",
"v1.16.1",
"v1.16.0",
"v1.15.2",
"v1.15.1",
"v1.15.0",
"v1.14.5",
"v1.12.1",
"v1.12.0",
"v1.11.3",
"v1.11.2",
"v1.11.1",
"v1.11.0",
"v1.10.7",
"v1.10.6",
"v1.10.5",
"v1.10.4",
"v1.10.3",
"v1.10.2",
"v1.10.1",
"v1.10.0",
"v1.9.1",
"v1.9.0",
"v1.8.2",
"v1.8.1",
"v1.8.0",
"v1.7.3",
"v1.7.2",
"v1.7.1",
"v1.7.0",
"v1.6.1",
"v1.6.0",
"v1.5.2",
"v1.5.1",
"v1.5.0",
"v1.4.2",
"v1.4.1",
"v1.4.0",
"v1.3.3",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v1.0.0-beta.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54630.json"
}
}
],
"modified": "2026-10-31T02:31:01.572572425Z",
"provider": "osv",
"references": [
"https://github.com/Part-DB/Part-DB-server/releases/tag/v2.12.1",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54630.json",
"https://github.com/Part-DB/Part-DB-server/security/advisories/GHSA-w5m7-3xf7-6g7g",
"https://nvd.nist.gov/vuln/detail/CVE-2026-54630"
],
"provider_metadata": {
"cwe_ids": [
"CWE-434"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54630.json"
}
},
"related_cves": [
{
"value": "CVE-2026-54630",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 496335,
"published_at": "2026-10-23T03:48:59.951+00:00"
}