CVE-2025-22634
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in MD Abu Jubayer Hossain Easy Booked – Appointment Booking and Scheduling Management System for WordPress easy-booked allows Cross Site Request Forgery.This issue affects Easy Booked – Appointment Booking and Scheduling Management System for WordPress: from n/a through <= 2.4.5.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Easy Booked WordPress plugin (versions up to 2.4.5). The plugin lacks proper anti-CSRF token validation on state-changing operations, allowing authenticated users to unknowingly execute unauthorized actions such as modifying appointments or settings through 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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 Easy Booked plugin is installedGo to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Easy Booked' in the listAffected if Easy Booked plugin is not installed on the WordPress site
-
Determine installed version of Easy BookedIn the Plugins list, find Easy Booked and note the version number displayed beneath the plugin nameAffected if Version is 2.4.5 or any version lower than 2.4.5
-
Identify state-changing endpointsInspect the plugin files (typically in wp-content/plugins/easy-booked) for AJAX handlers and form processing code that modify appointments or settings. Look for functions handling booking creation, modification, or deletion.Affected if The plugin contains forms or AJAX endpoints that perform state-changing operations (creating, updating, deleting appointments or modifying settings)
-
Check for nonce validation in state-changing codeExamine the identified form handlers and AJAX endpoints in the plugin code. Search for wp_verify_nonce, check_admin_referer, or nonces in the request handling functions. Look for missing or inadequate nonce verification.Affected if State-changing operations lack proper nonce verification or do not validate nonces at all before processing requests
A user is affected if Easy Booked plugin version 2.4.5 or lower is installed AND the site allows authenticated users to access state-changing operations that lack proper nonce validation.
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 WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints that perform state-changing operations, and verify these nonces on the server side before processing requests. Additionally, consider setting SameSite attribute on session cookies.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22634 — 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-22634 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