KitchenAsty up to 0.3.0 Reservations API reservation.controller.ts getReservation ID authorization

Summaryinfo

A vulnerability described as problematic has been identified in KitchenAsty up to 0.3.0. The affected element is the function getReservation of the file packages/server/src/controllers/reservation.controller.ts of the component Reservations API. The manipulation of the argument ID results in authorization. This vulnerability is known as CVE-2026-79348. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in KitchenAsty up to 0.3.0. Affected is the function getReservation of the file packages/server/src/controllers/reservation.controller.ts of the component Reservations API. The manipulation of the argument id with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality. CVE summarizes:

KitchenAsty through 0.3.0 contains a broken object level authorization (IDOR) vulnerability in the reservations API. The endpoint GET /api/reservations/:id in packages/server applies the authenticate middleware but performs no ownership or role check, and the getReservation handler in packages/server/src/controllers/reservation.controller.ts returns the record retrieved by the client-supplied identifier without comparing reservation.customerId to the authenticated principal

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-79348 since 08/25/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 09/29/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• KitchenAsty

Version

• 0.1
• 0.2
• 0.3.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion