CVE-2025-7517
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 · uneditedA 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 /getDay.php. The manipulation of the argument cidval 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 confidenceA critical SQL injection vulnerability exists in the Online Appointment Booking System 1.0 at the /getDay.php endpoint. The 'cidval' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The exploit is publicly available, making immediate remediation critical.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the application installationSearch for the file 'getDay.php' in your web server's document root directories. Common paths include /var/www/html/, /var/www/, C:\xampp\htdocs\, or the web root of your hosting environment.Affected if The file getDay.php exists in your web directory, indicating the vulnerable application is installed.
-
Verify the application versionInspect the application's source files for a version identifier. Check index.php, about.php, or any README/license files for version '1.0' or 'Anisha Online Appointment Booking System'.Affected if The installed version is confirmed as 1.0, matching the affected version.
-
Confirm the vulnerable endpoint existsCheck that the file /getDay.php exists and contains code that processes a 'cidval' parameter. Use 'grep -i cidval getDay.php' or open the file directly to inspect its contents.Affected if The getDay.php file contains logic that handles the cidval parameter without visible sanitization.
-
Identify if the application is exposed to the networkReview your web server configuration to confirm that the directory containing getDay.php is accessible via HTTP/HTTPS from untrusted networks. Check firewall rules and web server access logs for requests to this endpoint.Affected if The getDay.php endpoint is reachable from the network and not restricted by IP whitelisting or authentication.
-
Check for web application firewall protectionInspect your WAF, reverse proxy, or application-level security configurations to determine if SQL injection filtering is enabled for the /getDay.php endpoint.Affected if No WAF or SQL injection filtering is in place, leaving the cidval parameter unprotected.
You are affected if the Anisha Online Appointment Booking System version 1.0 is installed and the getDay.php endpoint with the cidval parameter is network-accessible without security controls.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for all database operations involving the cidval parameter. Alternatively, use a web application firewall as a temporary mitigation until code fixes are applied.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7517 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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