dbcve.org
Simple Student Information SystemApplication · Campcodes

CVE-2024-0497

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability was found in Campcodes Student Information System 1.0. It has been classified as critical. Affected is an unknown function of the file /classes/Users.php?f=save. The manipulation of the argument username leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-250602 is the identifier assigned to this vulnerability.

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 confidence

SQL injection vulnerability in Campcodes Student Information System 1.0 allows remote attackers to inject malicious SQL code via the username parameter in the /classes/Users.php?f=save endpoint. The lack of input sanitization or parameterized queries enables attackers to manipulate SQL queries, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in the Users.php save function, implement strict input validation on all user-supplied parameters, and apply any vendor security patches. Consider deploying a WAF as a temporary compensating control.

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
Simple Student Information 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
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 checks

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

  1. Confirm Campcodes Student Information System is installed
    Locate the application web root directory and look for the main PHP files or folder structure typical of Campcodes web applications
    Affected if The application files are present on the server
  2. Verify the installed version is 1.0
    Check version information in any README, about page, or configuration file within the application, or compare the Users.php file against known 1.0 release artifacts
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable file exists
    Check for the existence of /classes/Users.php in the web application directory
    Affected if The file /classes/Users.php exists in the application
  4. Check if the save function handles username without parameterized queries
    Open /classes/Users.php and examine the 'save' function code, specifically looking at how the username parameter is used in SQL queries - look for direct string concatenation or interpolation of the username variable into SQL statements
    Affected if The code shows username is directly inserted into SQL queries without using prepared statements or parameter binding
  5. Verify the application processes the username parameter at the /classes/Users.php?f=save endpoint
    Test if the endpoint accepts a username parameter by reviewing the application routing or by checking if the save function processes $_POST or $_GET['username']
    Affected if The application accepts and processes a username parameter through this endpoint

A user is affected if they have Campcodes Simple Student Information System version 1.0 with the /classes/Users.php file containing unsanitized username input in the save function that is accessible via the web.

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 prepared statements/parameterized queries in the Users.php save function, implement strict input validation on all user-supplied parameters, and apply any vendor security patches. Consider deploying a WAF as a temporary compensating control.

Fix this in Simple Student Information System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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