CVE-2025-7184
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 code-projects Library System 1.0. It has been classified as critical. This affects an unknown part of the file /user/teacher/books.php. The manipulation of the argument Search leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
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 Library System 1.0 at /user/teacher/books.php via the Search parameter. The lack of parameterized queries or input sanitization allows attackers to inject malicious SQL queries remotely, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.
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
- 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.
-
Confirm Library System installationLocate the web application root directory and identify if it contains a folder structure with /user/teacher/books.php. This is the vulnerable file path.Affected if The file /user/teacher/books.php exists in the web application directory
-
Verify product versionCheck the application's version identifier, typically found in a README file, about page, or version metadata within the source code. The affected version is 1.0.Affected if The installed Library System version is exactly 1.0
-
Inspect the vulnerable code in books.phpOpen /user/teacher/books.php and locate the SQL query handling the Search parameter. Look for direct string concatenation of user input into the SQL query, such as $sql = "SELECT * FROM books WHERE title LIKE '%" . $_POST['search'] . "%'". Without prepared statements or parameter binding, the vulnerability exists.Affected if The Search parameter is used in SQL queries via direct string concatenation without prepared statements or input sanitization
-
Confirm the Search parameter is accessibleVerify that the /user/teacher/books.php page accepts GET or POST requests with a 'search' parameter. This is the injection point for the attack.Affected if The Search parameter is accepted as user input on the books.php page without validation
A user is affected if they have Library System version 1.0 installed with the file /user/teacher/books.php present and the Search parameter handled via direct string concatenation in SQL 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 dataImplement prepared statements/parameterized queries for all database interactions in books.php, apply input validation and output encoding for the Search parameter, and conduct a comprehensive audit of the application for similar SQL injection vulnerabilities.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7184 — 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-2025-7184 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