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

CVE-2025-68052

HIGH · 8.8 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Unauthenticated Cross Site Request Forgery (CSRF) in Eagle Booking <= 1.3.4.3 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

An unauthenticated Cross Site Request Forgery (CSRF) vulnerability exists in Eagle Booking versions 1.3.4.3 and below, allowing attackers to trick authenticated users into performing unintended actions on the booking platform without their consent.

MitigationImplement anti-CSRF tokens on all state-changing forms and validate Origin/Referer headers to prevent forged requests from malicious sites.

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
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. Confirm Eagle Booking installation
    Check your web server for Eagle Booking files (typically in the web root directory, look for booking-related PHP files or the eagle-booking folder structure)
    Affected if Eagle Booking software is present on the server
  2. Identify installed version
    Check the version file or header in the Eagle Booking installation (commonly found in a version.php, config file, or admin dashboard about page)
    Affected if The installed version is 1.3.4.3 or lower
  3. Locate state-changing forms
    Identify forms that perform actions like bookings, user registration, or admin changes (search for HTML form elements in booking, reservation, or user management pages)
    Affected if Forms handling bookings or user data exist in the application
  4. Inspect for anti-CSRF tokens
    View the HTML source of state-changing forms and check if they contain anti-CSRF token fields (look for hidden input fields with names like token, csrf, nonce, or _token)
    Affected if State-changing forms lack anti-CSRF token fields in their HTML
  5. Verify Origin/Referer header validation
    Check server-side code or HTTP response headers to determine if the application validates the Origin or Referer headers on form submissions
    Affected if The application does not validate Origin or Referer headers on form submissions

You are affected if Eagle Booking version 1.3.4.3 or below is installed AND state-changing forms lack anti-CSRF token protection.

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 forms and validate Origin/Referer headers to prevent forged requests from malicious sites.

Have this fixed 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 help mitigating

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-2025-68052 — 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-2025-68052 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