InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure
InvoiceShelf is an open-source web & mobile app that helps track expenses, payments and create professional invoices and estimates. Prior to version 2.4.0, InvoiceShelf public customer invoice, estimate, and payment routes use an EmailLog token's numeric mailable_id without verifying mailable_type, and the JSON handlers do not enforce EmailLog::isExpired. A token issued for one document type can therefore disclose a different company's document when numeric identifiers collide, and an expired token can remain usable on the JSON routes GET /customer/invoices/{email_log:token}, GET /customer/estimates/{email_log:token}, and GET /customer/payments/{email_log:token}. View handlers can also mark a mismatched invoice or estimate as viewed and send a notification. This issue is fixed in version 2.4.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-55383
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 05:21 UTC · Revision 1
Source evidence
InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure
core-osv · Original sourcePublished 14 Oct 2026, 19:23 UTC
InvoiceShelf is an open-source web & mobile app that helps track expenses, payments and create professional invoices and estimates. Prior to version 2.4.0, InvoiceShelf public customer invoice, estimate, and payment routes use an EmailLog token's numeric mailable_id without verifying mailable_type, and the JSON handlers do not enforce EmailLog::isExpired. A token issued for one document type can therefore disclose a different company's document when numeric identifiers collide, and an expired token can remain usable on the JSON routes GET /customer/invoices/{email_log:token}, GET /customer/estimates/{email_log:token}, and GET /customer/payments/{email_log:token}. View handlers can also mark a mismatched invoice or estimate as viewed and send a notification. This issue is fixed in version 2.4.0.
osv:CVE-2026-55383
Complete source record
{
"id": "34a43b814cfa246b115f615cc96c0b2113b9aec0eca683e209776fd1442e29ed",
"url": "https://osv.dev/vulnerability/CVE-2026-55383",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure",
"summary": "InvoiceShelf is an open-source web & mobile app that helps track expenses, payments and create professional invoices and estimates. Prior to version 2.4.0, InvoiceShelf public customer invoice, estimate, and payment routes use an EmailLog token's numeric mailable_id without verifying mailable_type, and the JSON handlers do not enforce EmailLog::isExpired. A token issued for one document type can therefore disclose a different company's document when numeric identifiers collide, and an expired token can remain usable on the JSON routes GET /customer/invoices/{email_log:token}, GET /customer/estimates/{email_log:token}, and GET /customer/payments/{email_log:token}. View handlers can also mark a mismatched invoice or estimate as viewed and send a notification. This issue is fixed in version 2.4.0.",
"evidence": "osv:CVE-2026-55383",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-55383",
"aliases": [
"CVE-2026-55383",
"GHSA-73q7-2953-8gvx"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/invoiceshelf/invoiceshelf",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "e3ab12ad773749668dc64e029d265a8440e21477"
},
{
"fixed": "5839d8385debf379644f55e773639e1c7e673163"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "5839d8385debf379644f55e773639e1c7e673163"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "e3ab12ad773749668dc64e029d265a8440e21477"
}
],
"source": "REFERENCES_TAG",
"original_tag": "2.4.0"
}
]
}
}
],
"versions": [
"2.3.3",
"2.3.2",
"2.3.1",
"2.3.0",
"2.2.1",
"2.2.0",
"2.1.1",
"2.1.0",
"2.1.0-RC1",
"2.0.0",
"2.0.0-RC1",
"1.3.0",
"1.2.2",
"1.2.1",
"1.2.0",
"1.1.0",
"1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-55383.json"
}
}
],
"modified": "2026-10-28T02:30:33.499076311Z",
"provider": "osv",
"references": [
"https://github.com/InvoiceShelf/InvoiceShelf/releases/tag/2.4.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55383.json",
"https://github.com/InvoiceShelf/InvoiceShelf/security/advisories/GHSA-73q7-2953-8gvx",
"https://nvd.nist.gov/vuln/detail/CVE-2026-55383",
"https://github.com/InvoiceShelf/InvoiceShelf/commit/5839d8385debf379644f55e773639e1c7e673163",
"https://github.com/InvoiceShelf/InvoiceShelf/pull/662"
],
"provider_metadata": {
"cwe_ids": [
"CWE-285"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55383.json"
}
},
"related_cves": [
{
"value": "CVE-2026-55383",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 500485,
"published_at": "2026-10-14T19:23:33.527+00:00"
}