Authenticated SSRF via unsanitized invoice notes
Published Mar 31, 2026 · Updated Mar 31, 2026
SSRF in InvoiceShelf before 2.2.0 allows remote authenticated users to make server-side requests through invoice PDF rendering. Invoice Notes HTML is inserted unescaped into Blade templates, and Dompdf dereferences attacker-controlled image and link URLs. Company-level invoice access is required; requests can reach internal services or cloud metadata, while file reads and code execution require permissive Dompdf settings.
Summary
What happened
SSRF in InvoiceShelf before 2.2.0 allows remote authenticated users to make server-side requests through invoice PDF rendering. Invoice Notes HTML is inserted unescaped into Blade templates, and Dompdf dereferences attacker-controlled image and link URLs. Company-level invoice access is required; requests can reach internal services or cloud metadata, while file reads and code execution require permissive Dompdf settings.
The record
- CVE
- CVE-2026-34367
- Published
- Mar 31, 2026
- Updated
- Mar 31, 2026
- Vendor
- InvoiceShelf
- Product
- InvoiceShelf
- Classifications
- CWE-918, T1552.005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 2026CVE publishedPublication date reported by the CVE source.
- Mar 31, 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=< 2.2.0
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
- GitHub advisory proof of conceptproof of concept · demonstrated
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