dbcve.org
Rezgo Online BookingWordPress extension · Rezgo

CVE-2024-53800

HIGH · 8.1 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 4.17.1 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in rezgo Rezgo rezgo allows PHP Local File Inclusion.This issue affects Rezgo: from n/a through <= 4.17.

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 PHP Local File Inclusion (LFI) vulnerability in Rezgo allows attackers to include arbitrary local files via unsanitized input in include/require statements, potentially leading to arbitrary code execution or disclosure of sensitive system files.

MitigationUpgrade to a patched version of Rezgo if available; otherwise, implement strict input validation with whitelist-based filtering and disable allow_url_include to prevent path traversal attacks.

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
Rezgo Online BookingWordPress extension
Affected:< 4.17.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Check the installed Rezgo version
    Locate the version file or admin panel in the Rezgo installation and compare the version number to 4.17.1. The version is typically found in a configuration file, an XML file, or displayed in the admin dashboard footer.
    Affected if The installed version is below 4.17.1 (for example, 4.17.0, 4.16.x, or earlier)
  2. Identify PHP file inclusion functions in the source code
    Search the Rezgo source code for include, require, include_once, or require_once statements that use variables without sanitization, particularly those that might receive input from query parameters or user-controllable sources.
    Affected if Unsanitized include/require statements that accept user input are found in the codebase
  3. Verify the web server user has access to sensitive system files
    Check file permissions on system files such as /etc/passwd, /etc/shadow, or configuration files outside the web root. Attempt to determine if the PHP process can read these files.
    Affected if The web server process has read access to sensitive system or configuration files that could be included via path traversal
  4. Confirm PHP allow_url_include setting
    Check the PHP configuration file (php.ini) for the allow_url_include directive. This setting controls whether URL-aware fopen wrappers are enabled for include/require statements.
    Affected if allow_url_include is enabled (set to On) in php.ini
  5. Test for path traversal vulnerability
    If you have access to test the application, attempt to include a known local file (such as a configuration file in the Rezgo installation) by manipulating input parameters that are used in include/require statements.
    Affected if The application successfully includes files outside the intended directory based on user-supplied input

The environment is affected if Rezgo Online Booking version is below 4.17.1 AND the application contains include/require statements that use unsanitized user input, allowing attackers to read arbitrary local files.

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.

dbcve · scoped
Upgrade available Upgrade to 4.17.1 or later
Fixed in 4.17.1
Interim mitigation

Upgrade to a patched version of Rezgo if available; otherwise, implement strict input validation with whitelist-based filtering and disable allow_url_include to prevent path traversal attacks.

Recommended fix High confidence

Rezgo Online Booking 4.17.1

  1. Download Rezgo Online Booking version 4.17.1 from the official vendor source
  2. Back up your current Rezgo installation and database before upgrading
  3. Replace the existing Rezgo files with the version 4.17.1 files
  4. Verify the upgrade was successful by checking the admin interface version number
  5. Test that the application functions normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rezgo Online Booking Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53800 — 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-2024-53800 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