dbcve.org
Checkfront Online Booking SystemWordPress extension · Checkfront

CVE-2023-44146

HIGH · 8.8 CVSS v3.1 Published 2023-10-06
Fix available
A fix is available. Upgrade to 3.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Checkfront Inc. Checkfront Online Booking System plugin <= 3.6 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in Checkfront Online Booking System plugin version 3.6 and below allows attackers to trick authenticated users into performing unintended state-changing actions on the booking platform.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate the Origin/Referer headers to ensure requests originate from legitimate sources.

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
Checkfront Online Booking SystemWordPress extension
Affected:< 3.7

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify Checkfront version
    Locate the version information for your Checkfront installation (typically found in the admin dashboard under system info, or in a version file within the installation directory)
    Affected if The installed version is 3.6 or below (versions prior to 3.7)
  2. Confirm authenticated user access
    Determine if user accounts with login credentials exist in your Checkfront system
    Affected if Authenticated users can log in to perform actions on the booking platform
  3. Identify state-changing operations
    Review your Checkfront installation for endpoints that modify data (such as booking creation, booking cancellation, user profile updates, or payment processing)
    Affected if The system contains functionality that changes state via HTTP requests
  4. Inspect anti-CSRF token implementation
    Examine the HTML forms or API requests for state-changing operations and check for the presence of anti-CSRF tokens (synchronizer tokens) in the request parameters or headers
    Affected if No anti-CSRF tokens are present on state-changing operations
  5. Check Origin/Referer header validation
    Inspect the server-side code handling state-changing requests to verify if the Origin or Referer HTTP headers are validated against trusted sources
    Affected if Origin/Referer header validation is not implemented or is missing

You are affected if your Checkfront installation is version 3.6 or below and state-changing operations lack anti-CSRF token protection and Origin/Referer 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.

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

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate the Origin/Referer headers to ensure requests originate from legitimate sources.

Recommended fix Moderate confidence

Checkfront Online Booking System 3.7

  1. Identify the current installed version of Checkfront Online Booking System
  2. Locate and review the official Checkfront release notes for version 3.7 to understand changes
  3. Perform a complete backup of the Checkfront installation including database and files
  4. If possible, test the upgrade in a staging/development environment before production
  5. Upgrade the Checkfront Online Booking System to version 3.7 or later
  6. Verify the upgrade was successful by checking the version number in the admin interface
  7. Confirm the CSRF protection is functioning by testing form submissions
Caveat No breaking changes documented in the provided material; however, standard pre-upgrade backups are recommended

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

Fix this in Checkfront Online Booking System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,140
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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