CVE-2024-24096
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 · uneditedCode-projects Computer Book Store 1.0 is vulnerable to SQL Injection via BookSBIN.
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 confidenceCode-projects Computer Book Store 1.0 contains an SQL Injection vulnerability in the BookSBIN parameter, allowing attackers to inject malicious SQL queries via user input that is not properly sanitized before being used in database queries.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Computer Book Store application is presentSearch for web application files, processes, or services running on the server that match 'Computer Book Store' or 'BookStore'Affected if The application is installed and accessible on the system
-
Verify the installed version is 1.0Check the application version information in the source code, configuration files, or About page. Common locations include version.txt, README files, or version variables in the main PHP/ASP files.Affected if The version is exactly 1.0 (Carmelo Computer Book Store)
-
Identify if the BookSBIN parameter is exposedLocate the web entry points (forms, URLs, APIs) that accept user input and look for parameters named 'BookSBIN' or similar. Check the main application pages for search or filter functionality.Affected if The application has a parameter named BookSBIN that accepts user-supplied values
-
Inspect the input handling code for BookSBINReview the server-side code that processes the BookSBIN parameter. Look for database query construction where this parameter is used directly without visible sanitization functions (such as mysqli_real_escape_string, parameterized queries, or ORM methods).Affected if The BookSBIN parameter is used in SQL queries without prepared statements, parameter binding, or input validation
You are affected if the Carmelo Computer Book Store version 1.0 is running and the BookSBIN parameter accepts user input that is incorporated into SQL queries without sanitization or parameterization.
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 dataRemediate by replacing dynamic SQL queries with parameterized queries or prepared statements, and implement proper input validation on all user-supplied data before database operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24096 — 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-24096 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