dbcve.org
Library SystemApplication · Code Projects

CVE-2025-7179

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-08
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 vulnerability classified as critical was found in code-projects Library System 1.0. This vulnerability affects unknown code of the file /add-teacher.php. The manipulation of the argument Username leads to sql injection. The attack can be initiated 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 confidence

SQL injection vulnerability in the Library System 1.0 application where the Username parameter in /add-teacher.php is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for the Username parameter in add-teacher.php, and implement input validation as defense-in-depth.

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
Library SystemApplication
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. Confirm Library System version
    Search the application source files (index.php, about.php, or version files in the root) for version strings such as '1.0' or 'Library System 1.0'. Check any README or INSTALL files for version information.
    Affected if The installed version is Code Projects Library System 1.0
  2. Locate the vulnerable file
    Verify that add-teacher.php exists in the web application directory. Check the web root for the presence of this file at the path /add-teacher.php or \add-teacher.php.
    Affected if The file add-teacher.php exists in the application directory and is web-accessible
  3. Inspect Username parameter handling
    Open add-teacher.php and locate the code handling the Username parameter from the login or form submission. Examine how this parameter is incorporated into SQL queries - look for direct string concatenation or interpolation into SQL statements without using prepared statements or parameter binding.
    Affected if The Username parameter is used in a SQL query without prepared statements, parameter binding, or sanitization functions (such as mysqli_prepare, PDO::prepare, or real_escape_string)
  4. Verify SQL query execution
    In add-teacher.php, identify the database connection and query execution lines. Confirm that the Username value is passed directly to functions like mysql_query, mysqli_query, or PDO::query without parameterization.
    Affected if SQL queries containing the Username parameter are executed directly against the database without parameterized query handling

You are affected if you are running Code Projects Library System version 1.0 with the add-teacher.php file accessible and the Username parameter processed in SQL queries without prepared statements or input sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries for the Username parameter in add-teacher.php, and implement input validation as defense-in-depth.

Recommended fix Low confidence
  1. 1. Locate the vulnerable file /add-teacher.php in the application directory
  2. 2. Find the SQL query that uses the Username argument without proper sanitization
  3. 3. Replace the direct string concatenation in SQL queries with prepared statements using PDO or MySQLi
  4. 4. For PDO: Use $pdo->prepare('INSERT INTO teachers (Username, ...) VALUES (:username, ...)') with $stmt->bindParam(':username', $username)
  5. 5. For MySQLi: Use $stmt = $mysqli->prepare('INSERT INTO teachers (Username, ...) VALUES (?, ...)') with $stmt->bind_param('s', $username)
  6. 6. Apply the same parameterized query pattern to all user-supplied inputs in add-teacher.php
  7. 7. Test the fixed add-teacher.php functionality to ensure teachers can still be added correctly
  8. 8. Review other PHP files in the application for similar SQL injection vulnerabilities and apply the same fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Library System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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