dbcve.org
Library SystemApplication · Code Projects

CVE-2025-7199

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, which was classified as critical, has been found in code-projects Library System 1.0. This issue affects some unknown processing of the file /notapprove.php. The manipulation of the argument ID leads to sql injection. The attack may 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 · moderate confidence

SQL injection vulnerability in code-projects Library System 1.0 at /notapprove.php via the ID parameter. An unauthenticated remote attacker can manipulate SQL queries through the ID argument, potentially achieving complete database compromise.

MitigationImplement parameterized queries (prepared statements) for all database operations involving the ID parameter. Apply input validation and output encoding. Consider deploying a WAF as an interim control until the code fix is deployed.

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. Identify Code Projects Library System installation
    Locate the web application directory. Common paths include /var/www/html/, /wwwroot/, or the document root of your web server. Look for files indicating the Library System application (e.g., index.php, header files mentioning 'Library System' or 'code-projects').
    Affected if The Code Projects Library System application is present on the server.
  2. Verify installed version is 1.0
    Check for a version file, README, or any file containing 'version' or '1.0'. Also check the main index.php or config files for version strings. Compare your installed version against the affected range (= 1.0).
    Affected if The installed version is exactly 1.0.
  3. Confirm notapprove.php exists
    Navigate to the web application root and check for the presence of /notapprove.php file. If accessible via web, attempt to access the endpoint directly (e.g., http://target/notapprove.php).
    Affected if The notapprove.php file exists in the web application directory.
  4. Verify application has database connectivity
    Check config files (config.php, db.php, connection.php, or similar) for database credentials and connection strings. The SQL injection requires an active database connection to be exploitable.
    Affected if The application is configured with an active database connection.
  5. Test ID parameter acceptance
    If the application is accessible, send a request to notapprove.php with an ID parameter (e.g., ?id=1) and observe the response. The vulnerability exists if the application processes this parameter without proper sanitization.
    Affected if The notapprove.php script accepts and processes an ID parameter without parameterized queries.

You are affected if Code Projects Library System version 1.0 is installed, notapprove.php exists, and the ID parameter is processed without prepared statements.

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

Implement parameterized queries (prepared statements) for all database operations involving the ID parameter. Apply input validation and output encoding. Consider deploying a WAF as an interim control until the code fix is deployed.

Recommended fix Low confidence
  1. 1. Locate the /notapprove.php file in the Library System 1.0 installation
  2. 2. Identify the SQL query that uses the 'ID' parameter without proper sanitization
  3. 3. Replace dynamic SQL queries with prepared statements (parameterized queries)
  4. 4. Alternatively, use a database abstraction layer like PDO with prepared statements
  5. 5. Apply input validation on the ID parameter to ensure it contains only expected data types
  6. 6. Implement least-privilege database user account that only has necessary permissions
  7. 7. Test the remediation by attempting the SQL injection payload
  8. 8. Deploy the fixed /notapprove.php to production

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

Fix this in Library System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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