CVE-2023-7101 — Spreadsheet::ParseExcel Remote Code Execution Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (metasploit)+12
- EPSS 19.1% (30-day exploitation probability)+15
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.openwall.com (NIST National Vulnerability Database)
- Documented patch (NIST National Vulnerability Database)
CISA required action CISA
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
US federal deadline: Jan 23, 2024 — passed 996 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Douglas Wilson Spreadsheet::ParseExcel, Fedoraproject Fedora…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Douglas Wilson | Spreadsheet::ParseExcel | version 0.65 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Fedoraproject | Fedora | version 38version 39 | Vulnerable | NIST National Vulnerability Database |
| Jmcnamara | Spreadsheet::parseexcel | ≤ 0.65 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.8 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Barracuda ESG Spreadsheet::ParseExcel Arbitrary Code Execution excellent Dec 24, 2023
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 19.11%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
- Hunt retroactively in logs from before Jan 2, 2024 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · douglas wilson/spreadsheet::parseexcel
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · jmcnamara/spreadsheet::parseexcel, debian/debian linux, fedoraproject/fedora
- CVSS changed · 7.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2024
- Added to CISA KEV catalog
- 2023
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
12 on the record
- www.openwall.com/lists/oss-security/2023/12/29/4
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- github.com/mandiant/Vulnerability-Disclosures/blob/master/2023/MNDT-2023-0019.md
- github.com/advisories/GHSA-3c85-mx4x-435c
- security.metacpan.org/2024/02/10/vulnerable-spreadsheet-parsing-modules.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M2FIWD
- nvd.nist.gov/vuln/detail/CVE-2023-7101
- github.com/jmcnamara/spreadsheet-parseexcel/blob/c7298592e102a375d43150cd002feed
- lists.debian.org/debian-lts-announce/2023/12/msg00025.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M2FIWD
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IFEHKU
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IFEHKU
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
- Medium CVE-2026-56968 Use of Uninitialized Resource in Gnu Sasl Jun 23, 2026
- Medium CVE-2026-54231 Abrt: unsanitized systemd journal content written to dump directory files enables content injection Jun 13, 2026
- High CVE-2026-54230 Abrt: event handler scripts follow symlinks when writing output files, allowing arbitrary file overwrites Jun 13, 2026
- High CVE-2026-49975 Apache HTTP Server: mod_http2 denial of service Jun 8, 2026
- High CVE-2026-9256 NGINX ngx_http_rewrite_module vulnerability May 22, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-7101 is "Spreadsheet::ParseExcel Remote Code Execution Vulnerability", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 19.11% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.