dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14701

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-05
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 7 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 vulnerability was detected in code-projects Internship Management System 1.0. This affects an unknown function of the file employer/details/change_password.php of the component Password Change Endpoint. The manipulation of the argument Current results in sql injection. The attack can be executed remotely. The exploit is now 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 employer/details/change_password.php file of Internship Management System 1.0. The 'Current' parameter (likely the current password field) is not properly sanitized before use in SQL queries, allowing an attacker to inject malicious SQL syntax. The attack can be exploited remotely and a public exploit exists.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in change_password.php, implement proper input validation and sanitization on all user inputs, and apply the principle of least privilege to database accounts.

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. Confirm Internship Management System installation
    Search for common installation paths (e.g., /var/www/html/, /htdocs/, C:\xampp\htdocs\) for the Internship Management System. Look for index.php or login.php files that reference 'Internship Management System'. Check for version identifiers in footer, about page, or README files.
    Affected if The system is running Internship Management System 1.0 or an unspecified version within the 1.x lineage.
  2. Locate the vulnerable file
    Check if the file employer/details/change_password.php exists in the web root directory. Common paths: /employer/details/change_password.php or /internship/employer/details/change_password.php.
    Affected if The file change_password.php exists in the employer/details/ directory.
  3. Identify if password change functionality is enabled
    Verify the employer/details/ directory is accessible and the change_password.php file is present. Check if the application's employer portal is active by attempting to access or listing the employer directory via the web server.
    Affected if The employer portal and change_password.php functionality is accessible and operational.
  4. Examine the SQL query handling in change_password.php
    Open change_password.php and search for the 'Current' parameter usage in SQL queries. Look for code patterns like $_POST['Current'] or $_GET['Current'] directly concatenated into SQL strings without proper escaping, parameter binding, or use of prepared statements.
    Affected if The 'Current' parameter is used directly in SQL queries without parameterized queries, prepared statements, or input sanitization functions like mysqli_real_escape_string.

If the system runs Internship Management System 1.0 with the change_password.php file present and the 'Current' parameter is handled in SQL queries without parameterization, 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 parameterized queries or prepared statements in change_password.php, implement proper input validation and sanitization on all user inputs, and apply the principle of least privilege to database accounts.

Have this fixed 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-2026-14701 — 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-14701 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