CVE-2026-14700
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 · uneditedA security vulnerability has been detected in code-projects Internship Management System 1.0. The impacted element is an unknown function of the file employer/login.php of the component Employer Login Endpoint. The manipulation of the argument email/password leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly 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 confidenceSQL injection vulnerability in the employer/login.php file of the Internship Management System 1.0. The email and password parameters are not properly sanitized, allowing remote attackers to inject malicious SQL commands through the login endpoint.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Internship Management System installationSearch the web server document root for files named 'login.php' within an 'employer' directory, or look for typical installation paths such as /var/www/html/, /www/, or C:\inetpub\wwwroot\. Identify the presence of files indicating this specific application.Affected if The system is found installed on the server
-
Identify the installed versionCheck for a version file, README, or any file containing version metadata within the application root. Common locations include version.php, README.txt, or the footer/meta tags of index.php. Compare the found version against the known affected version 1.0.Affected if The installed version is 1.0 or the version cannot be determined (treat as potentially affected)
-
Verify the vulnerable file existsLocate employer/login.php within the web application directory structure. Confirm the file exists by checking the filesystem or accessing the URL https://[target]/employer/login.php.Affected if The file employer/login.php exists and is accessible via web
-
Confirm SQL injection vulnerability in source codeOpen employer/login.php and inspect the code handling the email and password POST parameters. Look for unsanitized variables used directly in SQL queries, such as $sql = "SELECT * FROM users WHERE email='$email' AND password='$password'". The vulnerability exists if these parameters are concatenated directly into the query string without using prepared statements or escaping functions.Affected if The code uses direct string concatenation for email/password in SQL queries without parameterization
If the Internship Management System version 1.0 is installed and employer/login.php contains unsanitized email/password parameters in SQL queries, the environment is affected by CVE-2026-14700.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements in employer/login.php, or implement proper input validation and escaping for the email and password fields.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14700 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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