CVE-2024-28279
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 book.php?bookisbn=.
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 confidenceSQL Injection vulnerability in Code-projects Computer Book Store 1.0 allows remote attackers to inject malicious SQL queries via the bookisbn parameter in book.php. The application fails to properly sanitize user input before using it 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify application versionLocate the application files and check for version identifiers in the source code, such as version numbers in headers, readme files, or configuration files. Look for 'Code-projects Computer Book Store' version 1.0.Affected if The application is Code-projects Computer Book Store version 1.0
-
Locate book.php fileSearch the web server document root for the book.php file, which is the vulnerable component mentioned in the CVE.Affected if The file book.php exists in the application directory
-
Inspect bookisbn parameter handlingOpen book.php and examine how the bookisbn parameter is processed. Look for code that retrieves this parameter from GET or POST requests (e.g., $_GET['bookisbn'] or $_POST['bookisbn']) and uses it directly in SQL queries without visible sanitization or prepared statements.Affected if The bookisbn parameter is retrieved from user input and used in SQL queries without parameterized queries or visible input sanitization
-
Verify unsanitized SQL query constructionSearch the book.php file for SQL query strings (SELECT, INSERT, UPDATE, DELETE) that concatenate or interpolate the bookisbn variable directly into the query string, rather than using placeholders with prepared statements.Affected if SQL queries concatenate the bookisbn value directly into the query string without escaping functions or prepared statement placeholders
You are affected if you are running Code-projects Computer Book Store version 1.0 and the bookisbn parameter in book.php is used in dynamically constructed SQL queries without proper sanitization or prepared statements.
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) and implement proper input validation on the bookisbn parameter. Conduct a full code audit to identify and remediate similar SQL injection vulnerabilities throughout the application.
- 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-28279 — 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-28279 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