Live › vulnerability › CVE-2026-86020
Go to dashboardPart-DB writes attacker-supplied part fields into XLSX exports without neutralising leading formula characters, so an imported value like =1+1 becomes a live formula cell. When another user exports the parts and opens the spreadsheet, their spreadsheet software may evaluate the formula.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running self-hosted Part-DB before 2.13.2 where some users can import parts from CSV and others export those parts to XLSX. Instances where only trusted administrators import data, or that do not use XLSX export, carry much less risk.
No product ranges from the sources yet.
2.13.2 are affected.2.13.2 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Part-DB is an open source inventory management system for electronic components. Prior to version 2.13.2, Part-DB contains a spreadsheet formula injection vulnerability in the part import/export workflow. An authenticated user with permission to import parts can import a CSV file containing formula-prefixed values, such as =1+1, into user-controlled part fields. When the affected part is later exported as an XLSX spreadsheet, Part-DB writes the attacker-controlled value using PhpSpreadsheet's setCellValue() method without neutralising spreadsheet formula characters. As a result, the exported XLSX file contains an executable spreadsheet formula cell rather than a plain text value. If another user exports and opens the spreadsheet, the formula may be evaluated by their spreadsheet software. This issue has been patched in version 2.13.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-86020")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.