dbcve.org
Online Student Clearance SystemApplication · Senior Walter

CVE-2025-5984

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 has been found in SourceCodester Online Student Clearance System 1.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /Admin/add-fee.php. The manipulation of the argument txtamt leads to cross site scripting. The attack can be launched 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

Cross-site scripting (XSS) vulnerability in SourceCodester Online Student Clearance System 1.0 at /Admin/add-fee.php. The txtamt parameter accepts unsanitized user input that is reflected back in the response without proper output encoding, allowing execution of arbitrary JavaScript in the context of the victim's browser.

MitigationImplement input validation and output encoding for the txtamt parameter in add-fee.php. Use context-appropriate encoding functions when rendering user input in HTML, and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

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
Online Student Clearance 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 the installed product and version
    Locate the SourceCodester/Senior Walter Online Student Clearance System installation directory and check for version indicators such as a version.php file, readme.txt, or the footer of the application pages. Compare the found version to the affected version 1.0.
    Affected if The application is Senior Walter Online Student Clearance System version 1.0
  2. Verify the vulnerable file exists
    Check for the presence of the file add-fee.php in the /Admin/ directory of the web application root. Common paths: /Admin/add-fee.php or /admin/add-fee.php.
    Affected if The file add-fee.php exists in the Admin directory of the installation
  3. Check admin interface accessibility
    Verify the /Admin/ endpoint is accessible on the web server. Attempt to access the add-fee.php page directly via HTTP/HTTPS to confirm it responds.
    Affected if The admin interface and add-fee.php page are accessible without authentication restrictions or the authentication is bypassed
  4. Inspect the txtamt parameter handling
    Locate and examine the add-fee.php source code. Look for how the txtamt POST/GET parameter is handled and whether it is directly echoed or reflected in the HTML response without sanitization or encoding.
    Affected if The txtamt parameter value is directly output in the page response without htmlspecialchars or equivalent encoding applied
  5. Test the vulnerability (optional)
    If authorized, send a request to add-fee.php with a benign XSS payload in the txtamt parameter (e.g., <script>alert(1)</script>) and verify whether the payload executes in the browser response.
    Affected if The XSS payload is reflected verbatim in the response and executes when the page loads

You are affected if you have Senior Walter Online Student Clearance System version 1.0 installed with the add-fee.php file present and the txtamt parameter reflecting unsanitized input in the response.

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

Implement input validation and output encoding for the txtamt parameter in add-fee.php. Use context-appropriate encoding functions when rendering user input in HTML, and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Fix this in Online Student Clearance System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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