# CVE-2023-24058: Missing authorization in n/a

> Authenticated users can create and schedule events for other users by modifying the userId parameter, allowing unauthorized data modification.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-cfwr-wq2f-j365

## What is CVE-2023-24058?

CVE-2023-24058 is a medium-severity missing authorization vulnerability in n/a, published on 22 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Booked Scheduler 2.5.5 allows authenticated users to create and schedule events for any other user via a modified userId value to reservation_save.php. NOTE: 2.5.5 is a version from 2014; the latest version of Booked Scheduler is not affected. However, LabArchives Scheduler (Sep 6, 2022 Feature Release) is affected.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2023-24058?

It affects 1 product.


Products: Twinkletoessoftware Booked.

## How do I fix CVE-2023-24058?

No fix has been published for CVE-2023-24058 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-24058 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24058 exists.

## Other vulnerabilities in n/a

- [CVE-2019-9581](https://insights.sbomify.com/CVE-2019-9581/): File upload in n/a (high 8.8)
- [CVE-2022-30706](https://insights.sbomify.com/CVE-2022-30706/): Open redirect in Booked (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24058 and fix it if it is affected.

What it is: CVE-2023-24058 is a medium-severity missing authorization vulnerability in n/a, published on 22 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24058 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-24058/ (Markdown: https://insights.sbomify.com/CVE-2023-24058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-24058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-24058
- OSV: https://osv.dev/vulnerability/CVE-2023-24058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-24058/
Summaries are generated and may contain mistakes; the official description above is the record.