CVE-2022-2747
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 was found in SourceCodester Simple Online Book Store and classified as critical. This issue affects some unknown processing of the file book.php. The manipulation of the argument book_isbn leads to sql injection. The attack may be initiated remotely. The associated identifier of this vulnerability is VDB-206015.
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 confidenceA SQL injection vulnerability in SourceCodester Simple Online Book Store allows remote attackers to inject arbitrary SQL commands via the book_isbn parameter in book.php. The critical CVSS 9.8 score indicates the vulnerability is exploitable over the network without authentication.
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 dataall versionsCVSS 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 Simple Online Book Store installationSearch the web root directory for the presence of book.php or the application's main files (such as index.php, connection/config files)Affected if The application files are present on the server and accessible via web
-
Verify book.php handles the book_isbn parameterExamine the source code of book.php and search for occurrences of the 'book_isbn' variable or parameterAffected if The book_isbn parameter is processed in book.php without proper sanitization
-
Check for dynamic SQL query usageSearch the book.php file for SQL query patterns involving book_isbn, such as SELECT, INSERT, UPDATE, or DELETE statements concatenated with the parameterAffected if Dynamic SQL queries directly incorporate the book_isbn parameter without prepared statements or parameter binding
-
Test the parameter for SQL injectionSend a crafted request to book.php with book_isbn parameter containing SQL metacharacters (such as single quote ' or boolean-based payloads like ' OR '1'='1) and observe the responseAffected if The application returns SQL error messages or behaves differently based on the SQL payload, indicating unsanitized input processing
-
Review web server logs for SQL injection attemptsExamine access logs for requests to book.php containing SQL syntax in the book_isbn parameterAffected if SQL injection patterns are found in the logs targeting the book_isbn parameter
-
Check if the vulnerability is already patchedLook for evidence of parameterized queries or input validation in book.php (functions like prepare(), bind_param(), or explicit sanitization functions)Affected if No parameterized queries or input validation is found in the code handling book_isbn
If book.php exists, processes the book_isbn parameter, and uses dynamic SQL queries without prepared statements, the installation is affected by this CVE.
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 for the book_isbn parameter in book.php, and implement proper input validation to sanitize user-supplied values.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2747 — 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-2022-2747 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