Authenticated file overwrite via misresolved export paths
Published Sep 1, 2026 · Updated Sep 1, 2026
Path traversal in Spartner Laravel Excel 3.1.8 through 3.1.69 allows remote authenticated users to overwrite existing writable files. Disk::copy resolves the caller-controlled destination against the process working directory, then opens a matching path in rb+ mode outside Flysystem confinement. Exploitation requires an application to pass unsanitized user input as the export path and an existing target writable by PHP; an executable PHP target yields code execution.
Summary
What happened
Path traversal in Spartner Laravel Excel 3.1.8 through 3.1.69 allows remote authenticated users to overwrite existing writable files. Disk::copy resolves the caller-controlled destination against the process working directory, then opens a matching path in rb+ mode outside Flysystem confinement. Exploitation requires an application to pass unsanitized user input as the export path and an existing target writable by PHP; an executable PHP target yields code execution.
The record
- CVE
- CVE-2026-84374
- Published
- Sep 1, 2026
- Updated
- Sep 1, 2026
- Vendor
- Spartner
- Product
- Laravel Excel
- Classifications
- CWE-73, CWE-22, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.1.8, < 3.1.70
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo