CVE-2022-2770
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, which was classified as critical, was found in SourceCodester Simple Online Book Store System. Affected is an unknown function of the file /obs/book.php. The manipulation of the argument bookisbn leads to sql injection. It is possible to launch the attack remotely. VDB-206166 is the identifier assigned to this vulnerability.
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 SourceCodester Simple Online Book Store System's book.php file. The 'bookisbn' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The critical CVSS score of 9.8 indicates potential for complete compromise of the database and potentially the application.
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 System installationSearch your web server directories for files matching 'book.php' or directories containing 'bookstore' or 'Simple-Online-Book-Store' in the path. Common locations include /var/www/html, /www, or C:\inetpub\wwwroot.Affected if The application files are found on the server
-
Identify the book.php file with the vulnerable parameterExamine the book.php file in the application root. Search for occurrences of the string 'bookisbn' within the file. Verify if this parameter is used in SQL query contexts without visible sanitization functions such as mysqli_real_escape_string, prepared statements, or parameter binding.Affected if The book.php file exists and processes the 'bookisbn' parameter in raw SQL queries without sanitization
-
Confirm the application is web-accessibleCheck your web server configuration (Apache httpd.conf, Nginx config, or IIS bindings) to confirm the Simple Online Book Store System directory is accessible via HTTP/HTTPS. Attempt a basic HTTP request to the book.php endpoint using its known URL path.Affected if The application is accessible over the network and the book.php endpoint responds to requests
-
Check for input handling on the bookisbn parameterReview the book.php source code around the 'bookisbn' parameter handling. Look for $_GET or $_POST usage retrieving 'bookisbn' and check if that value is directly concatenated into SQL queries or passed to database functions without escaping/binding.Affected if The 'bookisbn' parameter is received from user input and used in SQL queries without prepared statements or escaping
You are affected if the Simple Online Book Store System is installed and the book.php file processes the 'bookisbn' parameter in SQL queries without proper sanitization or parameterized queries.
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 or prepared statements. Implement proper input validation and sanitization for the bookisbn parameter. Apply principle of least privilege to database accounts.
- 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-2022-2770 — 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-2770 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