CVE-2026-57747
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 · uneditedUnauthenticated Cross Site Request Forgery (CSRF) in Booked <= 3.0.0 versions.
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 · moderate confidenceUnauthenticated Cross Site Request Forgery (CSRF) vulnerability in Booked scheduling plugin versions 3.0.0 and below allows attackers to trick authenticated users into performing unintended actions (such as making reservations or modifying bookings) via maliciously crafted requests.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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.
-
Verify Booked plugin is installedAccess WordPress admin panel and navigate to Plugins, or inspect plugin directory for 'booked' folderAffected if Booked scheduling plugin is present in the WordPress installation
-
Determine installed versionCheck plugin version in WordPress admin (Plugin Details) or read version in plugin's main file headerAffected if Version is 3.0.0 or lower (including any 2.x releases)
-
Inspect state-changing forms for CSRF tokensView source of booking forms, reservation submission pages, and user profile update forms; search for hidden token fields (such as 'nonce', 'token', or 'csrf' parameters)Affected if No anti-CSRF token field is present in forms that make reservations or modify bookings
-
Verify token validation on form submissionExamine plugin source code (booked-*.php files) for nonce verification calls (wp_verify_nonce, check_ajax_referer, or similar) before processing state-changing requestsAffected if No nonce verification found before executing reservation or booking modification actions
-
Check SameSite cookie attribute configurationInspect HTTP response headers for booking-related cookies (login, session, or appointment cookies) and verify SameSite attribute is setAffected if SameSite attribute is missing or set to 'None' without Secure flag on session cookies
User is affected if Booked plugin version 3.0.0 or below is installed AND state-changing operations lack anti-CSRF token validation AND SameSite cookies are not properly configured.
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 anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and configure SameSite cookie attributes to prevent cross-site request forgery attacks.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57747 — 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-57747 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