dbcve.org
Online Teacher Record Management SystemApplication · Campcodes

CVE-2025-5675

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-05
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 Campcodes Online Teacher Record Management System 1.0. It has been classified as critical. This affects an unknown part of the file /trms/admin/bwdates-reports-details.php. The manipulation of the argument fromdate/todate leads to sql injection. It is possible to initiate the attack 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 Campcodes Online Teacher Record Management System 1.0 admin panel. The bwdates-reports-details.php file accepts user-supplied input for the fromdate and todate parameters without proper sanitization or parameterized queries, allowing remote attackers to inject malicious SQL commands.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in bwdates-reports-details.php, or implement input validation and escaping for the fromdate and todate parameters.

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 Teacher Record 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 the application is Campcodes Online Teacher Record Management System
    Look for the application in your web server's document root or check installed packages. Look for files containing 'teacher record management' or the campcodes branding.
    Affected if The installed application is Campcodes Online Teacher Record Management System version 1.0
  2. Verify the exact version number
    Check the application's version information, typically found in README files, version metadata, or the admin dashboard about section. Compare against the affected version range.
    Affected if The version is exactly 1.0
  3. Locate the vulnerable PHP file
    Search for the file bwdates-reports-details.php in the web application directory structure, typically under the admin panel or reports functionality.
    Affected if The file bwdates-reports-details.php exists in the application
  4. Check if admin panel is accessible
    Attempt to access the admin panel login page or check web server access logs for requests to admin/ panel paths.
    Affected if The admin panel is publicly or internally accessible
  5. Inspect the vulnerable code in bwdates-reports-details.php
    Open bwdates-reports-details.php and search for direct use of $_GET or $_POST parameters 'fromdate' and 'todate' in SQL queries without prepare() statements, bindParam(), or escaping functions.
    Affected if The code shows fromdate/todate parameters concatenated directly into SQL queries without parameterized queries or input sanitization

You are affected if you have Campcodes Online Teacher Record Management System version 1.0 with the bwdates-reports-details.php file present and the admin panel accessible, where the fromdate/todate parameters are used unsafely 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 prepared statements/parameterized queries in bwdates-reports-details.php, or implement input validation and escaping for the fromdate and todate parameters.

Fix this in Online Teacher Record Management 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-5675 — 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-5675 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