CVE-2025-14537
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 weakness has been identified in code-projects Class and Exam Timetable Management 1.0. Affected by this issue is some unknown functionality of the file /preview7.php. This manipulation of the argument course_year_section/semester causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be exploited.
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 confidenceSQL injection vulnerability in code-projects Class and Exam Timetable Management 1.0 allows remote attackers to inject malicious SQL queries via the course_year_section or semester parameters in /preview7.php. The critical CVSS score of 9.8 indicates complete compromise potential including data exfiltration or database manipulation.
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= 1.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 installed product and versionLocate the Class and Exam Timetable Management System installation directory and check for version indicators such as a version file, about page, or header/footer copyright text showing the version number.Affected if The product is Fabian Class and Exam Timetable Management System version 1.0 exactly.
-
Verify preview7.php existsCheck for the presence of the file preview7.php in the web root or application directory of the installation.Affected if The file preview7.php exists in the application directory.
-
Inspect the preview7.php source codeOpen preview7.php in a text editor or use 'grep'/'findstr' to search the file contents for SQL query handling involving 'course_year_section' or 'semester' parameters.Affected if The file contains SQL queries that directly incorporate the course_year_section or semester parameters without visible parameterization or prepared statements.
-
Check input handling in preview7.phpReview the code around $_GET or $_POST requests for course_year_section and semester parameters to see if they are used in SQL statements without sanitization, escaping, or bound parameters.Affected if User-supplied input from course_year_section or semester parameters is concatenated directly into SQL queries without visible input validation or use of parameterized queries.
The system is affected if it is running Fabian Class and Exam Timetable Management System version 1.0 with the preview7.php file present and the vulnerable SQL query handling code that directly incorporates course_year_section or semester parameters into queries.
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.
dbcve · scopedReplace dynamic SQL queries with parameterized statements/prepared statements in preview7.php, validate and sanitize all user inputs, and apply input validation constraints on course_year_section and semester parameters.
- This product (Class and Exam Timetable Management System 1.0 from code-projects.org) is an abandoned student project with no vendor support or published security patches.
- If this system is in production use, migrate to a supported timetable management solution from a vendor that provides regular security updates.
- If the application must continue running temporarily, remove or restrict access to the vulnerable /preview7.php file via web server configuration (e.g., .htaccess deny or remove the file).
- Implement web application firewall (WAF) rules to block SQL injection attempts targeting the course_year_section and semester parameters.
- For permanent operation, refactor the application to use parameterized queries (PDO prepared statements) instead of raw SQL, though this requires significant code changes to an unmaintained codebase.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14537 — 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-14537 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