LubeLogger vulnerabilities

In LubeLogger prior to 1.6.8, `PrintRecordStickers` verifies access to the supplied `vehicleId` but fetches caller-supplied `recordIds` without checking that each record belongs to the authorized vehicle. An authenticated user can thus retrieve other users' records across multiple modules.

LubeLogger prior to 1.6.8 allows an authenticated user to submit caller-controlled recordIds to the DuplicateRecordsToOtherVehicles endpoint while naming destination vehicleIds the user can edit. The endpoint authorizes destination vehicles but fetches source records without checking UserCanEditVehicle for each existingRecord.VehicleId, allowing records belonging to another user to be copied into an attacker-controlled vehicle.

LubeLogger prior to 1.6.8 allows authenticated non-administrative users to reach HandleTranslationFileUpload and influence the name passed to RenameFile, which constructs newFilePath without verifying the resolved absolute path remains under the web root or data directory. A crafted upload name can move an uploaded file outside the intended storage directory.