CVE-2026-15137
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 weakness has been identified in code-projects Interview Management System 1.0. This vulnerability affects unknown code of the file \inc\classes\View.php. This manipulation of the argument ID causes sql injection. The attack can be initiated 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 confidenceSQL injection vulnerability in code-projects Interview Management System 1.0 in the file \inc\classes\View.php through the ID parameter, allowing remote attackers to inject malicious SQL queries due to unsanitized user input being used directly in database queries.
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 the application is installedLook for the Interview Management System web application files, typically in the web root directory. Search for directories containing 'interview-management' or check for the presence of typical PHP application structure.Affected if The Interview Management System by code-projects is present on the server.
-
Verify the application versionCheck for a version file, README, or any file containing version information within the application root directory. Look for files like version.txt, README.md, or check the main index.php for version references.Affected if The installed version is Interview Management System 1.0.
-
Locate the vulnerable fileNavigate to the \inc\classes\ directory and verify the presence of View.php. This file should exist in the path: [webroot]\inc\classes\View.phpAffected if The file \inc\classes\View.php exists in the application directory.
-
Inspect the vulnerable code in View.phpOpen \inc\classes\View.php and search for code that processes an ID parameter in database queries. Look for SQL statements that use $_GET, $_POST, or $_REQUEST with the 'id' parameter without using prepared statements or escaping functions.Affected if The file contains SQL queries that directly use the ID parameter from user input without sanitization or parameterized queries.
-
Check if the ID parameter is exposedIdentify application endpoints that accept an ID parameter (e.g., through URL query strings or form submissions) and route to the vulnerable function in View.php. Test by reviewing the application's routing or parameter handling.Affected if The application exposes functionality that passes user-supplied ID values to the vulnerable query in View.php.
If the system runs Interview Management System 1.0 with the file \inc\classes\View.php present and that file contains unsanitized ID parameter usage in SQL queries, the environment is affected by CVE-2026-15137.
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 dataImplement parameterized queries (prepared statements) for all database operations using the ID parameter, and apply proper input validation to prevent SQL injection attacks.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15137 — 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-15137 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