dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-57723

HIGH · 7.4 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in e4jvikwp VikBooking Hotel Booking Engine & PMS allows Path Traversal. This issue affects VikBooking Hotel Booking Engine & PMS: from n/a through 1.8.12.

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 · moderate confidence

A CSRF vulnerability in VikBooking Hotel Booking Engine & PMS versions up to 1.8.12 allows attackers to exploit authenticated administrator sessions to perform path traversal attacks, potentially reading sensitive files outside the web root by tricking admins into visiting malicious pages.

MitigationImplement anti-CSRF tokens on all state-changing endpoints and validate/sanitize all file path inputs to prevent directory traversal. Update to a patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Required
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify VikBooking installation
    Look for the VikBooking plugin/component in your CMS (Joomla/WordPress) or check for the 'vikbooking' directory in your web root. Check for files like 'vikbooking.php' or 'admin_vikbooking.php' in the components/plugins folders.
    Affected if VikBooking Hotel Booking Engine is installed on the system
  2. Determine installed version
    Check the version file or admin panel. For Joomla: go to Components > VikBooking > About, or check the manifest XML file (e.g., com_vikbooking.xml) in the installation package. Look for a version number in the format X.X.X.
    Affected if The installed version is 1.8.12 or any earlier version (e.g., 1.8.11, 1.8.10, etc.)
  3. Verify admin panel accessibility
    Check if the VikBooking admin panel is accessible via a web browser at paths like /administrator/index.php?option=com_vikbooking or similar admin URLs. Confirm whether administrator access is exposed to the internet.
    Affected if The administrator panel is accessible without network restrictions
  4. Check for anti-CSRF token implementation
    Inspect the HTML forms in the admin panel (especially file-related or settings forms) for hidden CSRF token fields. Look for elements named similar to 'csrf_token', 'token', or 'security_token' in POST requests. Use browser dev tools or capture a form submission to inspect the request payload.
    Affected if State-changing admin forms lack anti-CSRF token fields or the tokens are not validated server-side
  5. Check file path input validation
    Examine the backend code handling file operations (look for functions using file_get_contents, fopen, include, require with user-controlled paths). Check if paths are validated with functions like basename(), realpath(), or allowlist checks. Focus on any file read/include functionality in the admin area.
    Affected if File path inputs are not validated with sanitization functions or allowlist checks before being used in file operations

The environment is affected if VikBooking Hotel Booking Engine is installed and the version is 1.8.12 or earlier, with an accessible admin panel lacking anti-CSRF protections on endpoints that handle file paths without proper validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing endpoints and validate/sanitize all file path inputs to prevent directory traversal. Update to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57723 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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