> For the complete documentation index, see [llms.txt](https://blog.smithsecurity.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.smithsecurity.biz/booked-v2.5.5-labarchives-scheduler-vulnerability.md).

# Booked v2.5.5/LabArchives Scheduler Vulnerability

Hey you hackers,

I think I finally found my first CVE. It is a simple one but a new one none the less. This vulnerability in Booked Scheduler, tested on version 2.5.5 and the latest version of LabArchives Schedule, allows for authenticated users to create and schedule events for any other user as long as they have their user ID.

To do this it is as simple as changing the user ID in the HTTP POST request being sent to 'reservation\_save.php':

<figure><img src="/files/Zip82Ee1UYU8OAAurGZA" alt=""><figcaption></figcaption></figure>

My user ID is not 3 but 159 but changing the request UserId value to 3 created a reservation for the user with ID 3 and this is reflected when you go view the calendar page and see an event under that user name at the time and date specified.

This has been marked as [CVE-2023-24058](https://www.cve.org/CVERecord?id=CVE-2023-24058).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://blog.smithsecurity.biz/booked-v2.5.5-labarchives-scheduler-vulnerability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.