Skip to main content
CVE-2026-118061VulnerabilityPublished

The VikBooking Hotel Booking Engine & PMS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-118061· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 21 Nov 2026, 13:42 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

Since the vulnerability affects all versions up to 1.8.20, users should upgrade to a fixed version once available. Until then, consider disabling the vulnerable inquiry functionality or applying custom input sanitization and output escaping as a temporary mitigation. Monitor the vendor's advisory for official remediation updates.

Description

The VikBooking Hotel Booking Engine & PMS plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'inquiry (array keys)' parameter. This affects all versions up to and including 1.8.20. The vulnerability allows unauthenticated attackers to inject arbitrary scripts that execute when users access the affected pages. The injection is possible because the plugin does not properly sanitize or escape input. The only access control is a CSRF token that is publicly available on the inquiry page, making exploitation possible without authentication.

References

Community reviews

Loading reviews…