Skip to main content
VulnerabilityPublished Updated

CVE-2023-7101: Douglas Wilson Spreadsheet::ParseExcel · Eval Injection

Affects Douglas Wilson Spreadsheet::ParseExcelSource CVE Database V5

0

Exploited in the wild · KEV due 23 Jan 2024 · public exploit available (Metasploit) · 18% EPSS : apply the vendor's fix or mitigations to Douglas Wilson Spreadsheet::ParseExcel now.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS
18.9% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 24 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    1 Metasploit module

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 9 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Mandiant Inc.

    , 5 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. , 9 days after disclosure

  4. KEV remediation due

    US federal deadline

    , 30 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Douglas Wilson Spreadsheet::ParseExcelAffected
  • =0.65
Fixed in–

Description

Spreadsheet::ParseExcel version 0.65 is a Perl module used for parsing Excel files. Spreadsheet::ParseExcel is vulnerable to an arbitrary code execution (ACE) vulnerability due to passing unvalidated input from a file into a string-type “eval”. Specifically, the issue stems from the evaluation of Number format strings (not to be confused with printf-style format strings) within the Excel parsing logic.

References

Community reviews

Loading reviews…