Online Appointment Booking SystemApplication · Anisha

CVE-2025-7539

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A vulnerability, which was classified as critical, has been found in code-projects Online Appointment Booking System 1.0. This issue affects some unknown processing of the file /getdoctordaybooking.php. The manipulation of the argument cid leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

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

SQL injection vulnerability in the Online Appointment Booking System v1.0 allows remote attackers to inject malicious SQL queries via the 'cid' parameter in /getdoctordaybooking.php. The lack of input sanitization or parameterized queries on this parameter enables attackers to manipulate database queries, potentially extracting, modifying, or deleting sensitive data.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in /getdoctordaybooking.php to properly sanitize the 'cid' parameter input, and implement input validation. Consider applying a Web Application Firewall (WAF) as an additional layer of defense.

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
Online Appointment Booking SystemApplication
Affected:= 1.0

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

CVSS:3.1/AV:N/AC:L/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. Confirm application installation
    Locate the Online Appointment Booking System installation directory on the web server
    Affected if The application is present on the server and accessible via web
  2. Verify application version
    Check the version of the installed Online Appointment Booking System (typically in about.php, version file, or admin dashboard)
    Affected if Version is 1.0 exactly
  3. Locate vulnerable script
    Check if the file /getdoctordaybooking.php exists in the web root or application directory
    Affected if The file /getdoctordaybooking.php exists in the accessible web directory
  4. Identify cid parameter exposure
    Access the getdoctordaybooking.php script via HTTP request and observe if the 'cid' parameter is processed without sanitization (test with a benign payload like cid=1' to trigger SQL syntax error)
    Affected if The 'cid' parameter is accepted and processed by the script without proper input validation or parameterized queries
  5. Review source code for sanitization
    Inspect the getdoctordaybooking.php source code to verify whether the 'cid' parameter is passed directly into SQL queries without prepared statements, parameterized queries, or input sanitization functions
    Affected if The code contains direct SQL query construction using the 'cid' parameter without prepared statements or input sanitization

A user is affected if they are running Online Appointment Booking System version 1.0 with the /getdoctordaybooking.php script accessible and the 'cid' parameter handled without parameterized queries or input sanitization.

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

Replace dynamic SQL queries with prepared statements/parameterized queries in /getdoctordaybooking.php to properly sanitize the 'cid' parameter input, and implement input validation. Consider applying a Web Application Firewall (WAF) as an additional layer of defense.

Fix this in Online Appointment Booking System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-7539 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