CVE-2025-14565
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 identified in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. The affected element is an unknown function of the file /Profilers/SProfile/login1.php. Such manipulation of the argument Username leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might 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 confidenceSQL injection vulnerability in kidaze CourseSelectionSystem's /Profilers/SProfile/login1.php file, specifically in the Username parameter. This allows remote attackers to inject arbitrary SQL queries due to improper input sanitization, potentially enabling authentication bypass, data exfiltration, or database compromise.
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<= 2017-06-18CVSS 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 vulnerable login scriptSearch the web root for the file /Profilers/SProfile/login1.php. If using a Linux host: find /var/www -path '*/Profilers/SProfile/login1.php' 2>/dev/nullAffected if The file exists in the web application directory tree
-
Verify the application versionCheck the software version installed. This may be found in a VERSION file, about page, or header/footer include files within the kidaze application. Compare against the affected range: any version dated 2017-06-18 or earlierAffected if The installed version is 2017-06-18 or older, or if no version metadata is found but the application is confirmed as Kidaze CourseSelectionSystem
-
Confirm the login page is network accessibleAttempt to access the login endpoint via HTTP/HTTPS: GET /Profilers/SProfile/login1.php (or navigate to the application's login page and inspect the URL path)Affected if The login page is accessible without authentication over the network
-
Inspect the Username parameter handlingOpen login1.php and examine how the Username POST/GET parameter is processed. Look for direct insertion of the username into SQL queries without parameterized statements, prepared statements, or input sanitization functionsAffected if The code shows direct string concatenation of the Username parameter into SQL queries (for example: $sql = "SELECT * FROM users WHERE username='" . $_POST['username'] . "'")
The environment is affected if the Kidaze CourseSelectionSystem is installed with version 2017-06-18 or earlier, the file /Profilers/SProfile/login1.php exists, and the code contains unsanitized SQL queries using the Username parameter.
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 in login1.php, apply strict input validation on all user-supplied parameters, and implement least-privilege database accounts. Deploy a WAF as a temporary compensating control.
- 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-14565 — 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-14565 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