# CVE-2024-6660: Missing authorization in Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress

> Authenticated subscribers can update arbitrary options and upload files to escalate privileges to administrator due to missing capability checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pj78-8h7f-mg7f

## What is CVE-2024-6660?

CVE-2024-6660 is a high-severity missing authorization vulnerability in reputeinfosystems Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the bookingpress_import_data_continue_process_func function in all versions up to, and including, 1.1.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site and upload arbitrary files. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

Weakness: CWE-862 (Missing Authorization), CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2024-6660?

It affects 1 product.


Products: Reputeinfosystems Bookingpress.

## How do I fix CVE-2024-6660?

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

## Is CVE-2024-6660 being exploited?

There is no known exploitation of CVE-2024-6660 in the wild and no public exploit code.

## Other vulnerabilities in reputeinfosystems Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress

- [CVE-2022-0739](https://insights.sbomify.com/CVE-2022-0739/): BookingPress < 1.0.11 - Unauthenticated SQL Injection (critical 9.8)
- [CVE-2024-6467](https://insights.sbomify.com/CVE-2024-6467/): BookingPress Appointment Booking <= 1.1.5 - Authenticated (Subscriber+) Arbitrary File Read to Arbitrary File Creation (high 8.8)
- [CVE-2023-50841](https://insights.sbomify.com/CVE-2023-50841/): WordPress BookingPress Plugin <= 1.0.72 is vulnerable to SQL Injection (high 8.5)
- [CVE-2023-51405](https://insights.sbomify.com/CVE-2023-51405/): WordPress BookingPress plugin <= 1.0.74 - Booking Price Manipulation vulnerability (high 8.2)
- [CVE-2025-31910](https://insights.sbomify.com/CVE-2025-31910/): WordPress BookingPress plugin <= 1.1.28 - SQL Injection vulnerability (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6660 and fix it if it is affected.

What it is: CVE-2024-6660 is a high-severity missing authorization vulnerability in reputeinfosystems Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6660 in the wild and no public exploit code.

Affected product: reputeinfosystems Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress. 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-2024-6660/ (Markdown: https://insights.sbomify.com/CVE-2024-6660/index.md)
```

## Sources

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

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