CVE Alert: CVE-2025-9700 – SourceCodester – Online Book Store

CVE-2025-9700

HIGHNo exploitation known

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.

CVSS v3.1 (7.3)
Vendor
SourceCodester
Product
Online Book Store
Versions
1.0
CWE
CWE-89, SQL Injection
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Published
2025-08-30T17:32:07.386Z
Updated
2025-08-30T17:32:07.386Z

AI Summary Analysis

Risk verdict

High risk of remote, unauthenticated SQL injection with a publicly available exploit; requires immediate remediation.

Why this matters

Attackers can read or alter data via the vulnerable endpoint, potentially exfiltrating customer or transactional information. Given internet exposure, even limited success could lead to regulatory, financial, and reputational damage.

Most likely attack path

An attacker can reach the web endpoint over the internet and submit crafted pubid values to trigger unsafe SQL. No credentials or user interaction are required, so exploitation can occur directly through the application surface. Successful use could disclose or modify data and may enable limited data-layer traversal within the app.

Who is most exposed

Organisations hosting SourceCodester Online Book Store on internet-facing servers, especially small enterprises or providers with shared hosting or broad DB access, are most at risk due to common weak default security postures and limited monitoring.

Detection ideas

  • Look for anomalous pubid query strings and patterns suggesting injection
  • SQL error messages or unusual DB error codes in application logs
  • Spikes in 500s or long-running queries tied to publisher_list.php
  • IDS/WAF alerts for SQLi patterns (e.g., UNION SELECT, tautologies)
  • Unexpected data access or volume from the application’s DB user

Mitigation and prioritisation

  • Patch or upgrade to the fixed version; test in staging before production and deploy promptly
  • Replace dynamic SQL with parameterised queries; implement strict input validation
  • Enforce least-privilege DB access and restrict network paths to the DB; disable verbose error messages
  • Deploy WAF rules to block common SQL injection patterns; monitor and alert on anomalous DB activity
  • Change-management: plan a coordinated patch window, validate functionality post-patch, and communicate impact; If KEV true or EPSS ≥ 0.5, treat as priority 1.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.