dbcve.org
Vikbooking Hotel Booking Engine \& PmsWordPress extension · Vikwp

CVE-2023-32501

HIGH · 8.8 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 1.6.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in E4J s.R.L. VikBooking Hotel Booking Engine & PMS plugin <= 1.6.1 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the VikBooking Hotel Booking Engine & PMS plugin allows attackers to induce authenticated users to perform unintended actions (such as modifying bookings or settings) by tricking them into submitting malicious requests.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate these tokens server-side. Additionally, configure SameSite cookie attributes for session cookies.

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
Vikbooking Hotel Booking Engine \& PmsWordPress extension
Affected:< 1.6.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify VikBooking plugin is installed
    Locate the VikBooking plugin in your WordPress installation, typically under wp-content/plugins/vikbooking/, and check for the presence of plugin files.
    Affected if VikBooking plugin files are found in the WordPress plugins directory
  2. Determine installed version
    Access the WordPress admin dashboard under Plugins > Installed Plugins and locate the VikBooking entry to view the installed version number, or read the version from the plugin's main PHP file header.
    Affected if The installed version is lower than 1.6.2 (e.g., 1.6.1, 1.5.x, etc.)
  3. Inspect booking modification forms for CSRF tokens
    Navigate to a booking management page in the admin panel, view the HTML source of forms that modify bookings (edit, delete, update status), and check if each form includes a hidden input field containing a token value (such as 'csrf_token', 'token', or similar).
    Affected if Forms for modifying bookings do not contain any anti-CSRF token fields
  4. Inspect settings forms for CSRF tokens
    Navigate to the plugin settings pages in the WordPress admin, view the HTML source of forms that save configuration changes, and verify whether a token field is included in the form markup.
    Affected if Settings forms do not include CSRF token fields
  5. Check session cookie SameSite attribute
    Log into the WordPress admin, open browser developer tools (F12), go to the Application/Storage tab, examine session cookies (typically those with names like PHPSESSID, wordpress_sec_, or session identifiers), and check if the SameSite attribute is present in the cookie details.
    Affected if Session cookies lack the SameSite attribute or have it set to 'Lax' without proper token validation on the server side

Your environment is affected if the VikBooking plugin is installed with a version lower than 1.6.2 and state-changing operations lack CSRF token verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.6.2 or later
Fixed in 1.6.2
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate these tokens server-side. Additionally, configure SameSite cookie attributes for session cookies.

Recommended fix High confidence

1.6.2

  1. Backup your website and database before performing any upgrade
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find the Vikbooking Hotel Booking Engine & Pms plugin
  5. Check for update or deactivate the current version
  6. Install and activate version 1.6.2 or later from the WordPress plugin repository
  7. Verify the plugin is functioning correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vikbooking Hotel Booking Engine \& Pms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32501 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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