CVE-2026-1932
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 Appointment Booking Calendar Plugin – Bookr plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the update-appointment REST API endpoint in all versions up to, and including, 1.0.2. This makes it possible for unauthenticated attackers to modify the status of any appointment.
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 Bookr WordPress plugin has a missing authorization vulnerability in its REST API endpoint for updating appointments. The update-appointment endpoint does not perform capability checks or validate user permissions, allowing any unauthenticated request to modify appointment statuses. This is an IDOR-style authorization failure where the API trusts client input without verifying the requester's rights to modify the referenced appointment.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Identify if Bookr plugin is installedCheck the WordPress plugins directory or use WP-CLI: wp plugin list --name=bookr or inspect /wp-content/plugins/ for a bookr folderAffected if The Bookr plugin is present in the WordPress installation
-
Determine Bookr plugin versionAccess WordPress admin > Plugins > Bookr, or check the main plugin file header for the Version field, or use: grep -i 'Version:' /path/to/wp-content/plugins/bookr/*.phpAffected if The installed version matches or falls within the affected version range (verify against published vulnerable versions)
-
Confirm REST API endpoint exposureProbe the endpoint with a HEAD or GET request to common Bookr REST routes such as /wp-json/bookr/v1/appointments or /wp-json/bookr/update-appointment, or enumerate via /wp-json/Affected if The Bookr REST API endpoints are accessible and respond to requests
-
Test unauthenticated appointment modificationSend a POST request to the update-appointment endpoint with a valid appointment ID and modified status parameters (such as status=confirmed), without including any authentication headers or cookiesAffected if The request succeeds and modifies the appointment status without requiring authentication or authorization
-
Verify missing capability checksExamine the plugin source code in the REST API handler file (typically in includes/class-bookr-rest-api.php or similar) for current_user_can() or permission_callback checks on the update-appointment routeAffected if The endpoint handler lacks capability verification or permission_callback validation
A user is affected if the Bookr plugin is installed with a vulnerable version and the REST API update-appointment endpoint accepts and processes unauthenticated requests to modify appointment statuses.
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 dataImplement proper capability checks and user authorization validation in the update-appointment REST API endpoint. Until a patched version is available, consider restricting access to the REST API endpoint or deploying a WAF rule to limit unauthenticated appointment modifications.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1932 — 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-2026-1932 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