Vikbooking Hotel Booking Engine \& Property Management System PluginWordPress extension · Vikwp
CVE-2022-27863
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 · uneditedSensitive Information Exposure in E4J s.r.l. VikBooking Hotel Booking Engine & PMS plugin <= 1.5.3 on WordPress allows attackers to get the booking data by guessing / brute-forcing easy predictable booking IDs via search POST requests.
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 plugin for WordPress versions 1.5.3 and below allows unauthenticated attackers to access sensitive booking data due to predictable, sequentially-generated booking IDs. Attackers can enumerate valid booking IDs via search POST requests to retrieve customer personal information, booking details, and other confidential data.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Locate VikBooking plugin installationCheck if the directory /wp-content/plugins/vikbooking/ exists on the WordPress server filesystem or via FTP/SSH accessAffected if The plugin directory exists on the server
-
Determine installed plugin versionOpen the main plugin file (e.g., vikbooking.php) in the plugin directory and locate the version header comment, or check the readme.txt file for the 'Stable tag' version entryAffected if The version is 1.5.3 or lower (e.g., 1.5.2, 1.5.1, 1.5.0, etc.)
-
Verify sequential booking ID exposureSend a crafted POST request to the booking search endpoint (typically /index.php?option=com_vikbooking) with a range of sequential booking IDs (e.g., bookingid=1, bookingid=2, etc.) and observe if the response contains customer personal information, booking details, or reservation data without authenticationAffected if The search endpoint returns valid booking data for sequential ID values without requiring authentication or authorization validation
A WordPress site is affected if the VikBooking plugin version is 1.5.3 or lower and the booking search functionality returns sensitive data when queried with sequential booking IDs without authentication.
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 dataUpgrade to a patched version of the plugin that implements non-predictable booking identifiers (e.g., UUIDs) and adds proper authorization checks to ensure users can only access their own booking data.
Fix this in Vikbooking Hotel Booking Engine \& Property Management System Plugin
Scoped from the published advisory
- 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-2022-27863 — 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-27863 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