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

CVE-2023-25707

HIGH · 8.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to 1.6.0 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.5.12 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 for WordPress allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests, as the plugin lacks proper CSRF token validation on sensitive operations.

MitigationImplement anti-CSRF tokens (nonce validation) on all state-changing operations and forms within the plugin, and verify Origin/Referer headers on POST requests to prevent cross-site request forgery attacks.

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.0

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. Confirm VikBooking plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Vikbooking Hotel Booking Engine & PMS' or check the file system at wp-content/plugins/vikbooking for the plugin directory
    Affected if The VikBooking plugin is present in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find VikBooking, and read the version number displayed beneath the plugin name. Alternatively, check the 'vikbooking.php' main plugin file for the 'Version' header in the plugin comment block
    Affected if The version is below 1.6.0 (e.g., 1.5.x, 1.4.x, etc.)
  3. Locate sensitive state-changing operations
    Examine the plugin directory for PHP files handling form submissions, POST requests, or actions that modify data (e.g., booking submissions, settings changes, room management, customer data edits). Look for files in admin/ and front-end controllers that process user input
    Affected if The plugin processes any form submissions or POST requests that modify bookings, settings, or user data without requiring authentication verification
  4. Inspect code for CSRF token validation
    Open PHP files handling sensitive operations and search for 'nonce', 'wp_verify_nonce', 'wp_create_nonce', or 'check_admin_referer' functions. Verify that these validation functions are called before processing state-changing requests
    Affected if The sensitive operations lack nonce verification or the nonce checks are missing/disabled in the code handling the requests

You are affected if the VikBooking plugin is installed with a version lower than 1.6.0 and the plugin's sensitive operations (forms handling bookings, settings, or data modifications) lack proper CSRF token (nonce) validation in their code.

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.0 or later
Fixed in 1.6.0
Interim mitigation

Implement anti-CSRF tokens (nonce validation) on all state-changing operations and forms within the plugin, and verify Origin/Referer headers on POST requests to prevent cross-site request forgery attacks.

Recommended fix High confidence

1.6.0 or later

  1. 1. Create a complete backup of your Joomla! site and database before updating
  2. 2. Download VikBooking Hotel Booking Engine & PMS version 1.6.0 or later from the official source (Joomla! Extensions Directory or vendor)
  3. 3. Navigate to the Joomla! Administrator panel > Extensions > Manage > Install
  4. 4. Upload and install the new version, or use the update feature if available
  5. 5. Verify the update was successful by checking Extensions > Manage > Extensions shows version 1.6.0 or later
  6. 6. Test critical booking engine functionality including admin panel actions (add/edit reservations, settings changes) to confirm the update did not break existing workflows
Caveat Review release notes for any template or customization changes that may require adjustment

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25707 — 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-25707 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