CVE-2024-24092
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.org Scholars Tracking System 1.0 allows attackers to run arbitrary code via login.php.
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 login.php of the Scholars Tracking System 1.0 allows attackers to inject malicious SQL queries through unsanitized user input, potentially bypassing authentication or executing arbitrary database commands.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Scholars Tracking System installationSearch for directories containing 'scholars' or 'scholars_tracking' on the web server. Common paths include /var/www/html/, /www/html/, or C:\inetpub\wwwroot\. Also check for login.php files.Affected if The Scholars Tracking System application is present on the server.
-
Verify application versionCheck for version information in the application - look for a version.php file, about page, or readme.txt within the Scholars Tracking System directory. Compare the found version to 1.0.Affected if The installed version is Scholars Tracking System 1.0.
-
Identify login.php fileWithin the Scholars Tracking System directory, locate the login.php file. This is typically in the root directory or an admin/ folder.Affected if login.php exists in the application directory.
-
Inspect login.php for SQL injection vulnerabilityOpen login.php in a text editor or use 'grep' to search for SQL query patterns. Look for unparameterized queries like 'SELECT * FROM' or 'SELECT' concatenated with $_POST, $_GET, or $_REQUEST variables without using prepared statements or mysqli_real_escape_string/PDO::quote.Affected if login.php contains SQL queries that directly incorporate user input without sanitization or parameterized queries.
-
Check if login functionality uses dynamic SQLExamine the authentication logic in login.php. Look for user credentials (username/email and password) being used in SQL queries without mysqli_prepare, PDO::prepare, or escaping functions. Common vulnerable patterns include: $query = "SELECT * FROM users WHERE username='" . $_POST['username'] . "'".Affected if The login processing code builds SQL queries dynamically from user-supplied input without input sanitization or prepared statements.
A user is affected if they have Scholars Tracking System version 1.0 installed with a login.php that contains unsanitized SQL queries handling user authentication 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/prepared statements in login.php and validate all user inputs; apply vendor patch if available.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24092 — 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-24092 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