CVE-2025-14643
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 · uneditedA vulnerability was found in code-projects Simple Attendance Record System 2.0. The affected element is an unknown function of the file /check.php. Performing manipulation of the argument student results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could 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 confidenceA SQL injection vulnerability exists in the /check.php file of the Simple Attendance Record System 2.0. The vulnerability is located in the 'student' parameter, allowing remote attackers to inject malicious SQL queries. The attack can be exploited remotely without authentication and a public exploit is 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= 2.0CVSS 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.
-
Confirm the application is Simple Attendance Record System version 2.0Identify the running web application by examining application files, version metadata, or error messages. Check for version indicators in README files, configuration files, or the application source code.Affected if The application is Simple Attendance Record System but the version is not 2.0, or the version cannot be determined
-
Verify check.php exists in the web applicationLocate the check.php file within the application's web root directory. This is the file containing the vulnerability.Affected if check.php exists and is accessible via the web server
-
Examine the student parameter handling in check.phpOpen check.php and locate where the 'student' parameter is processed. Look for the code that handles this parameter and how it is used in database queries.Affected if The 'student' parameter is used in SQL queries without proper sanitization or parameter binding
-
Check for dynamic SQL query constructionReview the SQL query code in check.php. Identify whether the student parameter value is concatenated directly into SQL strings or if it is bound as a parameter using prepared statements.Affected if The student parameter is directly interpolated into SQL strings without using parameterized queries
You are affected if the Simple Attendance Record System version 2.0 is running and the check.php file uses the 'student' parameter in SQL queries without parameterized query implementation.
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 dataThe vulnerability should be remediated by replacing dynamic SQL queries with parameterized queries (prepared statements) in check.php, ensuring all user input is properly escaped or bound as parameters before database execution.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14643 — 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-14643 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