CVE-2025-14527
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 weakness has been identified in projectworlds Advanced Library Management System 1.0. This vulnerability affects unknown code of the file /view_book.php. Executing a manipulation of the argument book_id can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.
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 projectworlds Advanced Library Management System 1.0's /view_book.php file allows remote attackers to inject malicious SQL queries via the unsanitized book_id parameter. With CVSS 9.8, this critical flaw could enable authentication bypass, data exfiltration, or potential remote code execution depending on database configuration.
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 Projectworlds Advanced Library Management System is installedLocate the application web root directory and identify if the Advanced Library Management System is present. Check for version indicators in any version file, README, or about page.Affected if The installed version is exactly 1.0 (as indicated in affected versions)
-
Verify view_book.php existsNavigate to the web root of the application and locate the view_book.php file. This is the vulnerable script containing the SQL injection flaw.Affected if The file view_book.php exists in the application directory
-
Confirm network accessibilityDetermine if the application is accessible over HTTP/HTTPS from a network perspective. SQL injection requires the vulnerable endpoint to be reachable remotely.Affected if The view_book.php endpoint is reachable via network requests
-
Test book_id parameter for SQL injectionSend a crafted HTTP GET request to view_book.php with a SQL injection payload in the book_id parameter (e.g., book_id=1' OR '1'='1). Observe if the application returns unexpected database errors or altered query behavior.Affected if The application returns database SQL errors or exhibits unexpected behavior indicating unsanitized input is being interpreted as SQL
A user is affected if they have Projectworlds Advanced Library Management System version 1.0 deployed with view_book.php accessible over the network and the book_id parameter accepts unsanitized SQL input.
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 dataImmediately deploy parameterized queries/prepared statements for the book_id parameter in view_book.php and conduct a broader code review of the application for similar SQL injection vulnerabilities, as public exploits are available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14527 — 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-14527 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