dbcve.org
Online Book StoreApplication · Janobe

CVE-2025-9700

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-30
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
Public exploit 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 flaw has been found in SourceCodester Online Book Store 1.0. This issue affects some unknown processing of the file /publisher_list.php. This manipulation of the argument pubid causes sql injection. It is possible to initiate the attack remotely. The exploit has been published 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 confidence

SQL injection vulnerability in SourceCodester Online Book Store 1.0 where the 'pubid' parameter in /publisher_list.php is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The flaw has a CVSS score of 9.8 (Critical) and a public exploit exists.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the pubid parameter in publisher_list.php, perform input validation, and audit the entire application for similar SQL injection vulnerabilities.

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 Book StoreApplication
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. Locate the vulnerable file
    Search for publisher_list.php in the web root directory (commonly in /var/www/html/ or C:\inetpub\wwwroot\). Use: find /var/www -name "publisher_list.php" 2>/dev/null or dir /s /b C:\*publisher_list.php
    Affected if The file exists and the application is Janobe Online Book Store version 1.0
  2. Confirm application identity and version
    Check for version indicators such as a README file, version in footer, or admin/about page. Look for "Janobe Online Book Store" or "SourceCodester Online Book Store" version 1.0.
    Affected if The application is Janobe Online Book Store version 1.0
  3. Inspect the SQL query in publisher_list.php
    Open publisher_list.php in a text editor and locate the code handling the 'pubid' parameter. Search for SQL queries containing 'pubid' without prepared statements or escaping functions.
    Affected if The code contains a direct SQL query using $_GET['pubid'] or $_POST['pubid'] without sanitization functions like mysqli_real_escape_string, parameterized queries, or prepared statements
  4. Verify the parameter is accessible
    Attempt to access the URL pattern: http://target/publisher_list.php?pubid=1 Test with a benign value to confirm the parameter is processed.
    Affected if The page accepts the pubid parameter and returns database-driven content without error
  5. Check for SQL injection defense
    Review the publisher_list.php code around line handling pubid. Look for mysqli_prepare, PDO::prepare, or filtering/validation functions applied to pubid before SQL execution.
    Affected if No prepared statements, parameterized queries, or input validation are present for the pubid parameter

If publisher_list.php exists, the application is Janobe Online Book Store 1.0, and the pubid parameter is used in a raw SQL query without prepared statements or escaping, the environment is affected.

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 for the pubid parameter in publisher_list.php, perform input validation, and audit the entire application for similar SQL injection vulnerabilities.

Fix this in Online Book Store Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9700 — 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-2025-9700 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