VulnerabilityPublished 12 Dec 2025Updated 24 Feb 2026

CVE-2025-14566: kidaze CourseSelectionSystem · SQL Injection

Affects kidaze CourseSelectionSystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the absence of official patches, organizations should implement immediate compensating controls. First, apply strict input validation and sanitization on the USN parameter at the application level to block malicious SQL payloads. Employ parameterized queries or prepared statements to prevent direct injection of user input into SQL commands. Restrict database user privileges to the minimum necessary to limit the impact of any successful injection. Implement web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint. Monitor logs for unusual query patterns or repeated access to /Profilers/SProfile/reg.php with suspicious USN values. If possible, isolate the vulnerable system from direct internet exposure or restrict access via VPN or IP whitelisting. Stay alert for official patches or updates from kidaze and apply them promptly once available. Conduct regular security assessments and penetration testing to verify the effectiveness of mitigations.

Description

A security flaw has been discovered in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. The impacted element is an unknown function of the file /Profilers/SProfile/reg.php. Performing a manipulation of the argument USN results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.

Impact

The SQL injection vulnerability in kidaze CourseSelectionSystem can have severe consequences for organizations, particularly educational institutions managing course selections and student data. Exploitation can lead to unauthorized disclosure of sensitive information such as student identities, course enrollments, and academic records, violating privacy regulations and damaging institutional reputation. Attackers may also modify or delete data, undermining data integrity and potentially causing operational disruptions. In worst cases, attackers could escalate their access or pivot to other internal systems if database credentials or configurations are exposed. The remote, unauthenticated nature of the vulnerability increases the attack surface and risk, especially in environments exposed to the internet. The availability of a public exploit further elevates the threat, potentially leading to automated or widespread attacks. Organizations failing to address this vulnerability may face data breaches, compliance penalties, and loss of trust from students and stakeholders.

Summary

CVE-2025-14566 identifies a SQL injection vulnerability in the kidaze CourseSelectionSystem, specifically in an undisclosed function located in the file /Profilers/SProfile/reg.php. The vulnerability arises from improper sanitization or validation of the USN parameter, which is susceptible to malicious SQL payloads. This flaw allows an unauthenticated remote attacker to execute arbitrary SQL queries against the backend database by manipulating the USN argument. The vulnerability does not require any privileges or user interaction, making it highly accessible for exploitation. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low complexity, and no need for authentication or user interaction, but with limited impact on confidentiality, integrity, and availability. The scope remains unchanged, indicating the attack affects only the vulnerable component. Although no active exploitation has been reported, the public availability of an exploit increases the likelihood of attacks. The vulnerability could enable attackers to extract sensitive student or course data, alter records, or disrupt service availability, posing significant risks to educational institutions relying on this system. No official patches or mitigation links are provided yet, emphasizing the need for immediate defensive measures.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:56 UTC

Technical details

References

Community reviews

Related threats