dbcve.org
Online Bookstore WebsiteApplication · Keerti1924

CVE-2024-2272

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-08
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
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 classified as critical was found in keerti1924 Online-Book-Store-Website 1.0. This vulnerability affects unknown code of the file /home.php of the component HTTP POST Request Handler. The manipulation of the argument product_name leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-256042 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 /home.php allows remote attackers to inject arbitrary SQL commands via the product_name parameter in HTTP POST requests. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially extracting sensitive data, modifying records, or compromising the entire application.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) in /home.php for the product_name parameter. Implement strict input validation and apply output encoding. Deploy a WAF as a temporary compensating control until the code fix is complete.

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 Bookstore WebsiteApplication
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. Identify Keerti1924 Online Bookstore installation
    Locate the web application's document root directory and verify the presence of the application files, typically found in the web server's htdocs, www, or public_html directory.
    Affected if The application files for Keerti1924 Online Bookstore are present on the system.
  2. Confirm application version
    Check for version identification files such as README, version.php, or any file within the application that displays or contains '1.0' as the version number.
    Affected if The installed version is exactly 1.0.
  3. Locate vulnerable script
    Verify the existence of /home.php in the application's web-accessible directory.
    Affected if /home.php exists in the web root.
  4. Check for direct network accessibility
    Ensure the web server hosting the application is reachable over HTTP/HTTPS and the /home.php endpoint is accessible remotely.
    Affected if The application is exposed to network access and the /home.php endpoint responds to requests.
  5. Inspect parameter handling in home.php
    Open /home.php in a text editor or use 'grep' to search for occurrences of 'product_name' and verify whether the parameter is used directly in SQL queries without prepared statements, parameterized queries, or input sanitization.
    Affected if The product_name parameter from POST requests is concatenated directly into SQL queries without sanitization or parameterization.

A user is affected if they are running Keerti1924 Online Bookstore version 1.0 with /home.php accessible over the network and the product_name parameter handled without prepared statements in the code.

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 parameterized queries (prepared statements) in /home.php for the product_name parameter. Implement strict input validation and apply output encoding. Deploy a WAF as a temporary compensating control until the code fix is complete.

Fix this in Online Bookstore Website Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2024-2272 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