CVE-2024-40472
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 · uneditedSourcecodester Daily Calories Monitoring Tool v1.0 is vulnerable to SQL Injection via "delete-calorie.php."
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 confidenceSQL Injection vulnerability in delete-calorie.php of Sourcecodester Daily Calories Monitoring Tool v1.0 allows unauthenticated remote attackers to execute arbitrary SQL commands via unsanitized input parameters in the delete functionality.
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.
-
Confirm the Daily Calories Monitoring Tool versionLocate any version file, footer, or admin panel that displays the software version. Check source code for version strings like '1.0' or check the application README/installation files.Affected if The installed version is 1.0 of Rems/Daily Calories Monitoring Tool from Sourcecodester
-
Locate the delete-calorie.php fileSearch the web root directory for the file 'delete-calorie.php'. Common paths may include /delete-calorie.php or within a /php/ folder. Use file search commands or check the source code structure.Affected if The file delete-calorie.php exists in the application directory
-
Check if delete functionality uses dynamic SQLOpen delete-calorie.php and examine the database query code. Look for SQL statements that concatenate or embed user-supplied parameters directly into queries (e.g., 'DELETE FROM ... WHERE id=' . $_GET['id']) rather than using prepared statements with parameter binding.Affected if The code contains unsanitized SQL parameters passed directly from user input (GET/POST) into SQL queries without parameterized queries or input sanitization
-
Verify the application is accessible and accepting inputAttempt to access the delete-calorie.php endpoint via HTTP GET or POST request to confirm the application is running and the delete functionality is reachable.Affected if The application accepts requests to delete-calorie.php and processes input without immediate error blocking
You are affected if you are running Daily Calories Monitoring Tool version 1.0 and the delete-calorie.php file contains dynamic SQL queries that directly incorporate user input without parameterized queries or sanitization.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) in delete-calorie.php and all related database operations; validate and sanitize all user inputs.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-40472 — 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-2024-40472 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