dbcve.org
Student Information Management SystemApplication · Itsourcecode

CVE-2025-9839

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-02
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
Public exploit 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 security flaw has been discovered in itsourcecode Student Information Management System 1.0. The affected element is an unknown function of the file /admin/modules/course/index.php. Performing manipulation of the argument ID results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited.

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 itsourcecode Student Information Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /admin/modules/course/index.php. The application fails to properly sanitize or parameterize user input before using it in database queries.

MitigationFix requires implementing parameterized queries (prepared statements) in the vulnerable PHP file to properly sanitize the ID parameter before database execution. As a temporary measure, consider deploying a WAF rule to block SQL injection patterns.

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
Student Information Management 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. Locate the vulnerable PHP file
    Search for the file /admin/modules/course/index.php in the webroot directory of the itsourcecode Student Information Management System installation
    Affected if The file exists at this path, indicating the vulnerable application is present
  2. Confirm the application version
    Check the application version by examining any version file, footer, or about page in the installation. The vulnerability affects version 1.0 specifically
    Affected if The installed version is 1.0 exactly, matching the affected version range
  3. Verify admin module accessibility
    Attempt to access the /admin/modules/course/ directory via HTTP request to confirm the module is reachable
    Affected if The admin module is accessible without additional authentication restrictions beyond standard admin login
  4. Inspect the SQL query implementation
    Open /admin/modules/course/index.php and examine how the ID parameter is handled in SQL queries. Look for unsanitized concatenation of the ID parameter into SQL statements
    Affected if The code uses dynamic SQL (string concatenation) to build queries with the ID parameter rather than parameterized queries or prepared statements
  5. Check for other admin modules with similar patterns
    Review other PHP files in /admin/modules/ for similar patterns where request parameters are directly inserted into SQL queries without sanitization
    Affected if Additional admin modules contain similar unsanitized SQL query patterns

A defender is affected if they have itsourcecode Student Information Management System version 1.0 installed with the /admin/modules/course/index.php file present and that file uses dynamic SQL with the ID parameter.

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

Fix requires implementing parameterized queries (prepared statements) in the vulnerable PHP file to properly sanitize the ID parameter before database execution. As a temporary measure, consider deploying a WAF rule to block SQL injection patterns.

Fix this in Student Information Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9839 — 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-2025-9839 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