CVE-2026-14660
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 vulnerability was found in code-projects Online Job Portal 1.0. The affected element is an unknown function of the file login.php. Performing a manipulation of the argument txtUser/txtPass results in sql injection. The attack may be initiated remotely. The exploit has been made public and could 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 confidenceSQL injection vulnerability in the login.php file of Online Job Portal 1.0. The txtUser and txtPass parameters in the login form are not properly sanitized, allowing attackers to inject malicious SQL queries through the authentication inputs. This can lead to unauthorized access and potential database compromise.
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.
-
Confirm application is Online Job Portal v1.0Identify the web application by locating version identifiers in source files, about pages, or meta tags. Check for 'Online Job Portal' branding or version files in the webroot.Affected if The application is Online Job Portal version 1.0 and contains the vulnerable login.php file
-
Locate login.php in the web directoryFind the login.php file within the application web root, typically in the root directory or an /admin/ subfolder.Affected if login.php exists and handles authentication for the application
-
Inspect txtUser and txtPass parameter handlingOpen login.php and examine the code that processes the txtUser and txtPass POST/GET parameters from the login form. Look for the SQL query construction that uses these inputs.Affected if The code directly incorporates txtUser and txtPass values into a SQL query string without sanitization
-
Check for prepared statements or input validationSearch the login.php code for use of prepared statements (prepare, bind_param, parameterized queries), or input validation functions (escaping, whitelist validation) applied to txtUser and txtPass.Affected if No prepared statements, escaping, or input validation is found for these parameters in the SQL query
-
Verify dynamic SQL concatenation existsLook for string concatenation, string interpolation, or direct concatenation of txtUser/txtPass into the SQL query string (e.g., "SELECT * FROM users WHERE username='" . $txtUser . "'").Affected if The code builds SQL queries by directly concatenating user input from txtUser or txtPass parameters
If the application is Online Job Portal 1.0 and login.php directly uses txtUser/txtPass parameters in SQL queries without prepared statements or input validation, the environment is affected by this SQL injection vulnerability.
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 in login.php with parameterized queries (prepared statements) for the txtUser and txtPass parameters, and implement proper input validation. Apply the principle of least privilege to the database account used by the application.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14660 — 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-14660 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