CVE-2024-24093
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 · uneditedSQL Injection vulnerability in Code-projects Scholars Tracking System 1.0 allows attackers to run arbitrary code via Personal Information Update information.
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 confidenceA SQL injection vulnerability exists in the Personal Information Update functionality of Code-projects Scholars Tracking System version 1.0. Attackers can inject malicious SQL queries through unsanitized input fields in this module, potentially allowing execution of arbitrary database commands and potentially OS-level code execution depending on database configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Code-projects Scholars Tracking System installationSearch the web server document root or application directory for files named 'Scholars Tracking System', 'index.php', or similar application entry points. Check version.txt, README, or config files for the application name and version.Affected if The application is found and its version is 1.0
-
Identify the Personal Information Update moduleLook for PHP files or routes related to 'personal', 'update', 'profile', or 'information' in the application directory. Common paths may include /admin/, /user/, or /student/ subdirectories.Affected if A module or file handling personal information updates exists in the application
-
Examine the Personal Information Update code for dynamic SQL constructionOpen the identified personal information update PHP file and search for SQL query strings (SELECT, UPDATE, INSERT) that concatenate user input directly into query variables without using prepared statements or parameter binding.Affected if SQL queries are built using string concatenation or string interpolation with user-supplied input from $_POST, $_GET, or $_REQUEST variables
-
Verify input fields are not sanitizedReview the same PHP file for input validation functions such as mysqli_real_escape_string, htmlspecialchars, preg_match, or other sanitization applied to the input parameters before they are used in SQL queries.Affected if No sanitization functions are found applied to the input fields before they are used in SQL queries, or sanitization is incomplete (e.g., only trimming whitespace)
-
Confirm the module is accessible to untrusted usersDetermine if the personal information update functionality is accessible without authentication or via user accounts that could be obtained by an attacker (e.g., via registration). Check authentication logic in the update script.Affected if The update functionality is accessible to unauthenticated users or low-privilege accounts
The environment is affected if Code-projects Scholars Tracking System version 1.0 is installed, the Personal Information Update module exists, and its code constructs SQL queries using unsanitized user input.
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 or prepared statements in all Personal Information Update functions. Implement strict input validation and apply principle of least privilege to database accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24093 — 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-2024-24093 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