CVE-2025-12633
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Booking Calendar plugin for WordPress has a missing capability check on the '/wp-json/bookit/v1/commerce/stripe/return' REST API endpoint in versions up to 2.5.0. This allows unauthenticated attackers to connect their own Stripe account to the plugin, effectively hijacking payment processing and receiving customer payments intended for the site owner.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Bookit plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Booking Calendar | Appointment Booking | Bookit'. Note the installed version displayed.Affected if Plugin is installed and version is 2.5.0 or lower
-
Compare installed version to fixed releaseCheck the plugin version against the affected range. The vulnerability exists in versions up to and including 2.5.0. Version 2.5.1 contains the fix.Affected if Installed version is 2.5.0 or earlier
-
Verify Stripe integration is activeNavigate to the plugin settings in WordPress admin (usually under Bookit > Settings or similar). Look for Stripe/Payment settings. Check if Stripe is connected or enabled.Affected if Stripe integration is enabled and a Stripe account is configured in the plugin
-
Test REST API endpoint accessibilitySend a GET request to /wp-json/bookit/v1/commerce/stripe/return using curl or a browser. This endpoint should require authentication after the fix but was accessible without auth in vulnerable versions.Affected if Endpoint returns a valid response without requiring authentication (status 200 instead of 401)
User is affected if the Bookit plugin is installed with version 2.5.0 or earlier AND the Stripe integration is enabled, allowing unauthenticated access to the payment hijack endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Booking Calendar | Appointment Booking | Bookit plugin to version 2.5.1 or later which implements proper capability checks on the REST API endpoint. Until updated, consider disabling the Stripe integration or using an alternative booking solution.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data