Wp Hotel BookingWordPress extension · Thimpress
CVE-2021-36852
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 ThimPress WP Hotel Booking plugin <= 1.10.5 at WordPress.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in ThimPress WP Hotel Booking plugin versions 1.10.5 and below. The plugin fails to properly validate anti-CSRF tokens on state-changing requests, allowing attackers to trick authenticated WordPress users into unknowingly executing unintended actions such as modifying bookings, user settings, or administrative configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Hotel BookingWordPress extension
<= 1.10.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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.
-
Confirm WP Hotel Booking plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP Hotel Booking' or 'ThimPress WP Hotel Booking' in the list of active plugins.Affected if Plugin is not found in the installed plugins list, then this CVE does not apply.
-
Check the installed plugin versionIn the WordPress admin plugins list, locate WP Hotel Booking and note the version number displayed beneath the plugin name. Alternatively, check the plugin header in /wp-content/plugins/wp-hotel-booking/ or /wp-content/plugins/hotel-booking/ directory by reading the main plugin PHP file.Affected if The installed version is 1.10.5 or any version lower than 1.10.5.
-
Identify state-changing functionalityReview the plugin for features that modify data: booking management forms, user profile settings, room/booking creation, pricing configuration, and AJAX actions that create, update or delete records. Check if these forms include nonce fields (typically a hidden field named _wpnonce or similar).Affected if The plugin is at affected version AND contains forms or AJAX handlers that process state-changing requests without nonce token verification.
-
Verify nonce validation is absent in AJAX handlersExamine plugin PHP files in /includes/ and /classes/ directories for AJAX actions (add_action calls with wp_ajax_). Look for calls to wp_verify_nonce, check_admin_referer, or nonce verification functions. If handlers process requests without such verification, the vulnerability is present.Affected if AJAX endpoints exist that modify data without calling nonce verification functions before processing the request.
You are affected if the WP Hotel Booking plugin is installed at version 1.10.5 or lower and contains forms or AJAX actions that handle state-changing requests without proper anti-CSRF token 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 nonce verification on all forms and AJAX actions within the plugin. Add nonce fields to vulnerable forms and validate these nonces server-side before processing any state-changing requests. Also consider implementing SameSite cookie attributes. Update to the latest plugin version if a patched release is available.
Fix this in Wp Hotel Booking
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36852 — 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-2021-36852 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