dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15537

HIGH · 7.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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 security flaw has been discovered in SourceCodester Online Book Store System 1.0. This vulnerability affects unknown code of the file admin/login.php. The manipulation of the argument Username results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may 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 confidence

SQL injection vulnerability in SourceCodester Online Book Store System 1.0's admin/login.php script. The Username parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL statements. This could enable unauthorized admin access, data exfiltration, or potentially remote code execution depending on database configuration.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for the Username parameter and all user inputs. Implement input validation, apply least-privilege database accounts, and conduct a broader code audit for additional SQL injection vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Identify if SourceCodester Online Book Store System is installed
    Locate the application directory and check for files typical of this application (index.php, login pages, book-related modules). Check version.php or any version indicator if available.
    Affected if The application is SourceCodester Online Book Store System version 1.0 or the installed version cannot be determined but appears to be this system.
  2. Locate and examine admin/login.php
    Navigate to the admin/ directory and verify login.php exists. Open the file and search for the Username parameter handling, typically in $_POST or $_GET arrays.
    Affected if The file admin/login.php exists and processes a Username parameter without using prepared statements.
  3. Check for unsanitized SQL query construction
    Review the login.php code around the Username field. Look for SQL queries where the Username variable is concatenated directly into the query string (e.g., SELECT * FROM users WHERE username='$username').
    Affected if The Username parameter is inserted directly into an SQL query string without parameterized queries, escaping, or proper sanitization functions.
  4. Verify the login functionality is accessible
    Confirm the admin/login.php endpoint is reachable over the network (HTTP/HTTPS). Attempt a test request to verify the application responds to login attempts.
    Affected if The login page is publicly or internally accessible and accepts username input without apparent input validation.
  5. Confirm database user privileges
    Examine the database configuration file (often config.php, db.php, or similar in the application root). Identify the database user credentials used by the application.
    Affected if The application connects to the database with a user that has elevated privileges (e.g., root, admin, or user with DML/DDL permissions beyond read-only).

If SourceCodester Online Book Store System 1.0 is installed with admin/login.php accessible and the Username parameter is used in dynamically constructed SQL queries without prepared statements, the environment is affected by this SQL injection vulnerability.

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 prepared statements/parameterized queries for the Username parameter and all user inputs. Implement input validation, apply least-privilege database accounts, and conduct a broader code audit for additional SQL injection vulnerabilities.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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