dbcve.org
School Fees Payment Management SystemApplication · Campcodes

CVE-2025-13057

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-12
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 identified in Campcodes School Fees Payment Management System 1.0. Impacted is an unknown function of the file /ajax.php?action=save_student. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might 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 · moderate confidence

SQL injection vulnerability in Campcodes School Fees Payment Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter in /ajax.php?action=save_student. The application fails to properly sanitize user input before using it in SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements. Implement input validation and employ least-privilege database accounts. Apply vendor patch when available.

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 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. Confirm Campcodes School Fees Payment Management System is installed
    Locate the web application files in your web server root directory. Look for the presence of files such as ajax.php, index.php, or a directory structure containing 'school' or 'fees' related files.
    Affected if The application files are found in your web accessible directory.
  2. Identify the installed version
    Check for a version file, readme, or examine the main PHP files for version strings. Common locations include a version.php file, README.txt, or the footer/source code of index.php.
    Affected if The installed version is 1.0 exactly.
  3. Verify the vulnerable ajax.php endpoint exists
    Check if the file ajax.php exists in the web application directory. This file should handle the save_student action for the vulnerability to be present.
    Affected if ajax.php exists and is accessible via the web server.
  4. Confirm the save_student action handler exists
    Examine ajax.php source code to verify it contains a handler for 'save_student' action that processes the ID parameter. Look for code blocks handling $_POST['action'] == 'save_student'.
    Affected if The save_student action handler is present and processes an ID parameter.
  5. Check if user input reaches the database query unsanitized
    Review the save_student code path to determine if the ID parameter is directly concatenated into an SQL query without using prepared statements or proper escaping. Look for SQL queries using the ID value directly.
    Affected if The ID parameter is used directly in SQL queries without parameterized binding.

You are affected if you have Campcodes School Fees Payment Management System version 1.0 installed with the ajax.php endpoint handling save_student and the ID parameter is not sanitized before being used in SQL queries.

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 or prepared statements. Implement input validation and employ least-privilege database accounts. Apply vendor patch when available.

Fix this in School Fees Payment Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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