Authorization bypass in LubeLogger exposes other users' vehicle data
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
LubeLogger before 1.6.8 has an authorization flaw in the PrintRecordStickers function, which fetches caller-supplied record IDs without checking that they belong to the authorized vehicle (CWE-639). An authenticated user with low privileges can enumerate integer record IDs of other users and retrieve their vehicle maintenance records, including costs, notes, mileage and attachment metadata.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade LubeLogger to version 1.6.8, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
- Fix · CNA lubelog (hargata) Fixed in 1.6.8
Timeline
- 2026-10-30 Threatist record created from CVE-2026-62277
- 2026-11-01 Priority changed: MEDIUM → LOW
- 2026-11-02 CISA SSVC decision points changed
- 2026-11-02 Priority changed: LOW → MEDIUM
References
More hargata vulnerabilities
- TI-2026-44472 Path traversal in hargata lubelog CVSS 3.1HIGH 8.1
- TI-2026-44473 Authorization bypass in hargata lubelog CVSS 3.1HIGH 7.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences