Booking Calendar | Appointment Booking | Bookit <= 2.5.0 - Missing Authorization to Unauthenticated Stripe Connection
| CVE | CVE-2025-12633 |
|---|---|
| CVSS | 7.5 (High) |
| Publicly Published | November 11, 2025 |
| Last Updated | November 12, 2025 |
| Researcher |
Md. Moniruzzaman Prodhan (NomanProdhan)
- Knight Squad
|
Description
The Booking Calendar | Appointment Booking | Bookit plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the '/wp-json/bookit/v1/commerce/stripe/return' REST API Endpoint in all versions up to, and including, 2.5.0. This makes it possible for unauthenticated attackers to connect their Stripe account and receive payments.
References
Share
Vulnerability Details for Bookit — Booking & Appointment Calendar
| Software Type | Plugin |
|---|---|
| Software Slug | bookit (view on wordpress.org) |
| Patched? | Yes |
| Remediation | Update to version 2.5.1, or a newer patched version |
| Affected Version |
|
| Patched Version |
|
Recent vulnerabilities in Bookit — Booking & Appointment Calendar
| # | Title | CVE ID | CVSS | Researchers | Date |
|---|---|---|---|---|---|
| 1 | Bookit — Booking & Appointment Calendar <= 2.6.0.3 - Missing Authorization | CVE-2026-84767 | sungbyeongchan | September 3, 2026 | |
| 2 | Bookit — Booking & Appointment Calendar <= 2.5.1 - Missing Authorization | CVE-2026-40780 | davidfdzmorilla | April 22, 2026 | |
| 3 | Bookit <= 2.5.0 - Missing Authorization to Unauthenticated Settings Update | CVE-2025-12841 | Khaled Alenazi (Nxploited) | November 15, 2025 | |
| 4 | BookIt <=2.4.0 - Price Bypass | CVE-2024-24715 | Debangshu Kundu, Arpeet Rathi | January 31, 2024 | |
| 5 | BookIt <= 2.4.3 - Authenticated(Administrator+) SQL Injection | CVE-2023-50852 | Muhammad Daffa | December 21, 2023 | |
| 6 | Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_get | CVE-2023-33999 | Rafie Muhammad | July 18, 2023 | |
| 7 | BookIt <= 2.3.7 - Authentication Bypass | CVE-2023-2834 | István Márton | June 20, 2023 | |
| 8 | Freemius SDK <= 2.4.2 - Missing Authorization Checks | CVE-2022-4974 | March 4, 2022 |
This record contains material that is subject to copyright.
Copyright 2012-2026 Defiant Inc.
License: Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. Read more.
Copyright 1999-2026 The MITRE Corporation
License: CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. Read more.
Have information to add, or spot any errors? Contact us at wfi-support@wordfence.com so we can make any appropriate adjustments.
Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!
Learn moreWant to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.
The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.
Documentation