Vikbooking Hotel Booking Engine \& Property Management System PluginWordPress extension · Vikwp
CVE-2022-27862
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 · uneditedArbitrary File Upload leading to RCE in E4J s.r.l. VikBooking Hotel Booking Engine & PMS plugin <= 1.5.3 on WordPress allows attackers to upload and execute dangerous file types (e.g. PHP shell) via the signature upload on the booking form.
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 confidenceThe VikBooking Hotel Booking Engine WordPress plugin versions 1.5.3 and below contains an unauthenticated arbitrary file upload vulnerability in the signature upload functionality of the booking form. Attackers can upload dangerous file types (such as PHP shells) and execute them to achieve remote code execution on the server.
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 \& Property Management System PluginWordPress extension
<= 1.5.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 VikBooking plugin installationIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'VikBooking Hotel Booking Engine', or check the filesystem for the vikbooking folder under wp-content/plugins/Affected if The VikBooking plugin is installed and active in WordPress
-
Identify installed plugin versionView the plugin details in WordPress admin (click on the VikBooking plugin card) to read the version number, or open the main plugin file (vikbooking.php) and locate the Version header in the file commentsAffected if The installed version is 1.5.3 or lower (the vulnerable range)
-
Inspect upload directories for suspicious filesExamine the WordPress uploads folder (wp-content/uploads/ and subdirectories) for unexpected .php files, shell scripts, or other executable file types that could indicate exploitationAffected if Malicious files (especially PHP shells or executable scripts) are present in the upload directory
-
Verify booking form signature upload is enabledCheck the VikBooking settings for the booking form configuration to confirm whether the signature upload feature is enabled and accessible to unauthenticated usersAffected if The signature upload functionality is active and accessible without authentication
You are affected if the VikBooking plugin version is 1.5.3 or below AND the signature upload feature is enabled, particularly if suspicious executable files are found in the upload directories indicating possible exploitation.
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.
dbcve · scopedUpdate the VikBooking plugin to version 1.5.4 or later which contains the security patch. If immediate update is not possible, disable the plugin or implement WAF rules to block executable file uploads to the upload directory.
Latest version of VikBooking Hotel Booking Engine (newer than 1.5.3)
- Update VikBooking Hotel Booking Engine & Property Management System plugin to the latest available version from the WordPress plugin repository
- Navigate to Plugins > All Plugins in WordPress admin panel
- Locate VikBooking plugin and click 'Update Now' if an update is available
- After updating, verify the new version number in the plugins list
- Check the uploads directory for any suspicious files (especially .php files) that may have been uploaded during a potential attack
- Consider reviewing server access logs for any unusual file upload requests to the booking form signature upload feature
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vikbooking Hotel Booking Engine \& Property Management System Plugin
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-2022-27862 — 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-2022-27862 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