Computer Science Time Table SystemApplication · Carmelo

CVE-2024-24105

HIGH · 7.8 CVSS v3.1 Published 2024-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
SQL Injection vulnerability in Code-projects Computer Science Time Table System 1.0 allows attackers to run arbitrary code via adminFormvalidation.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 confidence

SQL Injection vulnerability in adminFormvalidation.php of Code-projects Computer Science Time Table System 1.0 allows attackers to inject malicious SQL queries, potentially leading to arbitrary code execution through database function abuse.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements, implement input validation, and apply least-privilege database user accounts.

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
Computer Science Time Table SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Time Table System application
    Search the web server document root for directories containing 'Time Table', 'timetable', or similar naming. Check for the presence of adminFormvalidation.php in admin or adminstration folders.
    Affected if The Code-projects Computer Science Time Table System is found on the server
  2. Verify the software version
    Check any version file, readme.txt, or the main index.php for version metadata. The affected version is exactly 1.0.
    Affected if The installed version is 1.0
  3. Confirm vulnerable file exists
    Locate adminFormvalidation.php in the application directory structure, typically under /admin/ or /adminstration/ path.
    Affected if adminFormvalidation.php exists in the application
  4. Check application accessibility
    Determine if the admin panel or adminFormvalidation.php is accessible via HTTP/HTTPS requests to the web server.
    Affected if The file is accessible via web requests without authentication or with valid admin credentials
  5. Inspect the vulnerable code pattern
    Open adminFormvalidation.php and search for direct SQL query construction using $_POST, $_GET, or $_REQUEST without parameterized queries or prepared statements.
    Affected if The code contains unsanitized user input in SQL queries

If the Code-projects Computer Science Time Table System version 1.0 is installed with the adminFormvalidation.php file accessible and containing dynamic SQL queries using user input, the environment is affected by CVE-2024-24105.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements, implement input validation, and apply least-privilege database user accounts.

Fix this in Computer Science Time Table System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24105 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24105 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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