Skip to main content
VulnerabilityPublished

CVE-2026-118061: VikBooking Hotel Booking Engine & PMS (WordPress plugin) · Cross-site Scripting

Affects VikBooking Hotel Booking Engine & PMS (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 21 Nov 2026, 09:44 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
e4jvikwpVikBooking Hotel Booking Engine & PMSAffected
  • <=1.8.20
Fixed in–

AI-suggested

Until a fix is available, administrators should consider disabling or restricting access to the vulnerable inquiry functionality to prevent exploitation. Monitoring for updates from the vendor and applying any forthcoming patches promptly is recommended.

Description

The VikBooking Hotel Booking Engine & PMS WordPress plugin is affected by a stored cross-site scripting (XSS) vulnerability in the 'inquiry (array keys)' parameter. This vulnerability exists in all versions up to and including 1.8.20 and allows unauthenticated attackers to inject malicious scripts that execute when users access the affected pages. The vulnerability arises from insufficient input sanitization and output escaping. The injection can be performed by any unauthenticated visitor because the only access control is a publicly available CSRF token on the inquiry page.

References

Community reviews

Loading reviews…