LubeLogger is a self-hosted, open-source, web-based vehicle maintenance and fuel mileage tracker. Prior to 1.6.8, `PrintRecordStickers` in `/Controllers/VehicleController.cs` checks through `CollaboratorFilter` that the authenticated caller can view the supplied `vehicleId`, but fetches caller-supplied `recordIds` without checking that each record's `VehicleId` belongs to the authorized vehicle. An authenticated user can submit `POST /Vehicle/PrintRecordStickers` with an authorized `vehicleId`, enumerate other users' integer record IDs and select an `ImportMode` to retrieve records across the service, gas, repair, upgrade, tax, supply, note, odometer, reminder, plan, inspection and equipment stores. Returned information includes descriptions, costs, notes, mileage, extra fields and file attachment metadata, allowing cross-user disclosure of vehicle maintenance records. This issue is fixed in version 1.6.8.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 6.5 · hargataNVD modified 2026-10-30 22:06
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 3
- https://github.com/hargata/lubelog/security/advisories/GHSA-8j7x-38m5-84xj x_refsource_confirm
- https://github.com/hargata/lubelog/commit/c8d5888ebc69e6a163e33f36200233ec845e5c57 x_refsource_misc
- https://github.com/hargata/lubelog/releases/tag/v1.6.8 x_refsource_misc