LubeLogger: IDOR in PrintRecordStickers Allows Unauthenticated Cross-User Vehicle Record Exfiltration
Affects LubeLogger 1.6.7 and earlier, where an authenticated user with View permission on one vehicle can read other users' vehicle maintenance records through PrintRecordStickers. Fixed in 1.6.8.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.6.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LubeLogger, a self-hosted open-source vehicle maintenance and fuel tracking web application, is affected before version 1.6.8. An authenticated user can access other users' vehicle records, including service, fuel, repair, cost, note, and attachment details, which exposes private maintenance information across accounts.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- hargata lubelog
fixed in 1.6.8
References 3
GitHub · hargata/lubelog
Questions about CVE-2026-62277
What does this mean?
The PrintRecordStickers endpoint does not properly check that the caller may access the vehicle requested, which is an insecure direct object reference (IDOR). A logged-in user can therefore read other users' vehicle records, including service history, costs, repair bills, notes, odometer readings and file attachment metadata.Source: github.com
Am I affected, and how do I check?
LubeLogger version 1.6.7 or earlier. The attacker needs an authenticated account with View permission on at least one vehicle they can access. To check an installation, compare its LubeLogger version against 1.6.8.Source: github.com
What should I do about it?
Upgrade LubeLogger to version 1.6.8 or later, which is the fixed release listed for this issue.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data