dbcve.org
School Fees Payment SystemApplication · Fabian

CVE-2025-5977

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-10
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 vulnerability was found in code-projects School Fees Payment System 1.0 and classified as critical. This issue affects some unknown processing of the file /datatable.php. The manipulation of the argument sSortDir_0 leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

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

A critical SQL injection vulnerability exists in the School Fees Payment System 1.0 at the /datatable.php endpoint. The sSortDir_0 parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code. This has a CVSS score of 9.8 (Critical) and a public exploit is available.

MitigationImmediate remediation requires replacing dynamic SQL queries with parameterized queries/prepared statements in the datatable.php file, implementing proper input validation for the sSortDir_0 parameter, and conducting a broader code review to identify similar injection points throughout the application.

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
School Fees Payment 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 School Fees Payment System installation
    Locate the application files on the server. Look for directories containing 'school' or 'fees' related PHP files, typically in the web root directory.
    Affected if The application files are present on the server.
  2. Verify the application version
    Check for version information in any README, version.php, or config files within the application directory. Compare against version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Confirm vulnerable endpoint exists
    Locate the datatable.php file within the application directory structure. This file should handle data table requests.
    Affected if The datatable.php file exists in the application.
  4. Check network accessibility
    Determine if the application is accessible over HTTP/HTTPS. Attempt to access the datatable.php endpoint from a browser or curl request.
    Affected if The application is accessible over the network.
  5. Verify parameter handling
    Send a test request to the datatable.php endpoint with a sSortDir_0 parameter. Observe whether the parameter value is reflected in SQL queries or if there is evidence of direct string concatenation.
    Affected if The sSortDir_0 parameter is accepted and used in SQL queries without sanitization.

The environment is affected if School Fees Payment System version 1.0 is installed and the datatable.php endpoint with the sSortDir_0 parameter is accessible and processes the parameter without SQL sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediate remediation requires replacing dynamic SQL queries with parameterized queries/prepared statements in the datatable.php file, implementing proper input validation for the sSortDir_0 parameter, and conducting a broader code review to identify similar injection points throughout the application.

Recommended fix High confidence
  1. Do not use School Fees Payment System 1.0 from code-projects.org in any production or sensitive environment.
  2. This is a student project/educational code from an unmaintained source that will not receive security updates.
  3. Replace with a commercially supported school fee management system that provides regular security patches.
  4. If continued use is required, implement a web application firewall (WAF) in front of the application to mitigate SQL injection attacks, though this is a compensating control not a fix.
Caveat No upgrade path available; this is an unmaintained educational project that should be replaced entirely rather than used.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in School Fees Payment System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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