dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7117

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 weakness has been identified in code-projects Employee Management System 1.0. Impacted is an unknown function of the file 370project/approve.php. Executing a manipulation of the argument id/token can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could 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 · moderate confidence

SQL injection vulnerability in code-projects Employee Management System 1.0 at file 370project/approve.php. The id/token parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands.

MitigationImplement parameterized queries/prepared statements for all database interactions involving user input. Apply input validation and sanitization on the id/token parameter. Consider deploying a WAF as an interim control while the code fix is being implemented.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the Employee Management System installation
    Search for the file path 370project/approve.php in your web root directory. Common locations include /var/www/html/, /www/, or C:\inetpub\wwwroot\ on Windows servers. Use 'find / -name approve.php 2>/dev/null' on Linux or search your web server document root.
    Affected if The file 370project/approve.php exists in your web application directory structure.
  2. Verify the application is reachable via HTTP/HTTPS
    Attempt to access the approve.php file through your web browser or curl command: curl -I https://yourdomain.com/370project/approve.php. Check if the server responds with 200 OK or a PHP error message rather than 404.
    Affected if The vulnerable file is web-accessible and responds to HTTP requests.
  3. Confirm a database backend is in use
    Review your application configuration files (such as db.php, config.php, or .env) in the 370project directory. Check for database connection strings pointing to MySQL, PostgreSQL, or SQLite. Also check if the application displays or manages employee records.
    Affected if The application uses a database backend for storing employee data, as SQL injection requires a SQL database to exploit.
  4. Inspect the approve.php source code for vulnerable parameter handling
    Open 370project/approve.php in a text editor. Search for occurrences of $_GET, $_POST, or $_REQUEST referencing 'id' or 'token'. Verify if these parameters are directly interpolated into SQL queries without using prepared statements, parameterized queries, or proper escaping functions like mysqli_real_escape_string or PDO::quote.
    Affected if The code shows direct insertion of id/token parameters into SQL queries without sanitization or prepared statement usage.
  5. Test for SQL injection vulnerability (if authorized)
    With explicit authorization, submit a benign SQL injection test payload to the id parameter, such as: 370project/approve.php?id=1' OR '1'='1. Observe if the application returns database errors, unexpected data, or behaves differently than with a normal numeric id value.
    Affected if The application reflects SQL syntax errors, returns unexpected data, or exhibits abnormal behavior when special SQL characters are passed in the id/token parameter.

Your environment is affected if the Employee Management System 1.0 is installed with the 370project/approve.php file web-accessible and the code directly uses unsanitized id/token parameters in SQL queries.

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

Implement parameterized queries/prepared statements for all database interactions involving user input. Apply input validation and sanitization on the id/token parameter. Consider deploying a WAF as an interim control while the code fix is being implemented.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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