Financial-record corruption via unchecked client-supplied totals
Published Oct 14, 2026 · Updated Oct 14, 2026
Input validation failure in InvoiceShelf before 2.4.0 allows remote authenticated users to falsify financial totals via document requests. InvoicesRequest::getInvoicePayload and the estimate and recurring-invoice handlers persist client-supplied totals without recalculating them from line items. A valid login is required; stored document totals can disagree with item prices and quantities.
Summary
What happened
Input validation failure in InvoiceShelf before 2.4.0 allows remote authenticated users to falsify financial totals via document requests. InvoicesRequest::getInvoicePayload and the estimate and recurring-invoice handlers persist client-supplied totals without recalculating them from line items. A valid login is required; stored document totals can disagree with item prices and quantities.
The record
- CVE
- CVE-2026-55384
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- InvoiceShelf
- Product
- InvoiceShelf
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Upstream document-total manipulation reproductionproof of concept · unverified
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started