CVE-2025-65135
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 · uneditedIn manikandan580 School-management-system 1.0, a time-based blind SQL injection vulnerability exists in /studentms/admin/between-date-reprtsdetails.php through the fromdate POST parameter.
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 confidenceA time-based blind SQL injection vulnerability exists in the School Management System version 1.0. The fromdate POST parameter in /studentms/admin/between-date-reprtsdetails.php is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code that uses time-delay functions to infer information from the database based on response times.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify School Management System v1.0 is installedLocate the School Management System installation directory. Check for version identifier files (such as version.php, README, or an admin panel that displays the version). Compare your installed version to the affected version 1.0.Affected if The installed version is School Management System 1.0.
-
Confirm the vulnerable PHP file existsCheck if the file /studentms/admin/between-date-reprtsdetails.php exists in your web root or application directory.Affected if The file between-date-reprtsdetails.php exists in the studentms/admin directory.
-
Inspect the source code for dynamic SQL usageOpen between-date-reprtsdetails.php and examine how the fromdate POST parameter is handled in SQL queries. Look for direct concatenation of the parameter into SQL strings (e.g., $sql = "SELECT * FROM table WHERE date = '" . $_POST['fromdate'] . "'") versus parameterized queries using prepared statements.Affected if The fromdate parameter is directly concatenated into SQL queries without using prepared statements or input sanitization.
-
Test the parameter for SQL injection responseSend a POST request to /studentms/admin/between-date-reprtsdetails.php with a benign fromdate value (e.g., '2025-01-01') and observe the response. Then send a time-based payload such as fromdate=2025-01-01' AND SLEEP(5)-- to see if the response is delayed.Affected if The application responds to time-delay SQL injection payloads in the fromdate parameter, confirming the vulnerability is exploitable.
You are affected if you have School Management System version 1.0 installed, the vulnerable PHP file exists, and the fromdate parameter is handled with dynamic SQL rather than prepared statements.
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) to prevent SQL injection. Validate and sanitize all user inputs, and apply the principle of least privilege to the database user.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65135 — 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-2025-65135 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