CVE-2026-62277

LubeLogger: IDOR in PrintRecordStickers Allows Unauthenticated Cross-User Vehicle Record Exfiltration

Published Oct 30, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

LubeLogger’s PrintRecordStickers endpoint performs an ownership check for the supplied vehicleId but fails to verify that each recordId actually belongs to that vehicle. An authenticated user can send a POST request with an authorized vehicleId and supply a list of arbitrary record identifiers. By selecting an ImportMode, the request retrieves detailed information from records belonging to other users’ vehicles. Exposed data includes descriptions, costs, notes, mileage, extra fields and file attachment metadata, enabling a full history of other customers’ maintenance activities. The flaw is an Authorization Bypass via User-Controlled Key, identified as CWE‑639.

Affected Systems

The vulnerability affects the LubeLogger application released by Hargata. Every version before 1.6.8 of LubeLogger is susceptible; the issue was addressed in release 1.6.8. Users running any older version should consider upgrading to mitigate the risk.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate impact, but the lack of an EPSS score suggests limited exploitation evidence at present. The issue is not listed in CISA’s KEV catalog, implying no known widespread exploitation. The attack vector requires an authenticated session to send a POST to /Vehicle/PrintRecordStickers, so the vulnerability is best characterized as authenticated, server-side data exfiltration through an IDOR flaw.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade LubeLogger to version 1.6.8 or later, which removes the IDOR check and enforces record ownership verification.
  • If an upgrade cannot be performed immediately, block public access to the PrintRecordStickers endpoint or ensure that the vehicleId parameter is bound to the authenticated user’s data before processing the request.
  • Add database-level validation so that every recordId supplied is verified to belong to the requester’s vehicle before any data is returned, preventing bypass even if the request is malformed.

Generated by OpenCVE AI on October 30, 2026 at 23:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Hargata
Hargata lubelog
Vendors & Products Hargata
Hargata lubelog
Type Values Removed Values Added
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.
Title LubeLogger: IDOR in PrintRecordStickers Allows Unauthenticated Cross-User Vehicle Record Exfiltration
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 2, 2026, 2:44 PM
Reserved
Jul 13, 2026, 6:37 PM
Status
Deferred
Published
Oct 30, 2026, 10:16 PM
Modified
Nov 2, 2026, 7:35 PM