CVE-2025-14536
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 security flaw has been discovered in code-projects Class and Exam Timetable Management 1.0. Affected by this vulnerability is an unknown functionality of the file /index.php of the component Login. The manipulation of the argument username/password results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may 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 · high confidenceA critical SQL injection vulnerability exists in the login functionality of the Class and Exam Timetable Management System v1.0 at /index.php. The username and password parameters are not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code and potentially extract, modify, or delete database contents including user credentials.
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.
-
Locate the Fabian Class and Exam Timetable Management System installationSearch the web server document root for files named 'index.php' or directories containing 'timetable' or 'class' in the path. Check web server configuration files (Apache nginx, IIS) for DocumentRoot paths pointing to this application.Affected if The application files are found on the server at any location
-
Verify the application versionCheck for a version file (version.php, README.txt, or similar) in the application root directory. If no version file exists, examine the source code of index.php for version comments or check the footer of login pages for version strings.Affected if The installed version is 1.0 exactly, or if version cannot be determined but the product matches Fabian Class And Exam Timetable Management System
-
Confirm the vulnerable login endpoint existsCheck for the presence of /index.php in the application directory. Examine the file content to verify it contains login form handling code with SQL query logic for username and password parameters.Affected if The file /index.php exists and contains login functionality with SQL query construction
-
Check if the login page is network accessibleIf the application is web-facing, attempt to access the login page via HTTP/HTTPS. Use a tool like curl or a browser to request the index.php page and verify it returns a login form.Affected if The login page at /index.php is accessible over the network and accepts username/password parameters
The environment is affected if the Fabian Class and Exam Timetable Management System version 1.0 is installed and the login page at /index.php is present and accessible, as the SQL injection flaw exists in that specific component.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) for all user input fields in the login component. Apply input validation and escaping for any remaining dynamic queries. If a vendor patch is available, apply it immediately.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14536 — 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-14536 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