CVE-2025-9679
BaseFortify
Publication date: 2025-08-30
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| facebook-julykringcadayona | student_information_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9679 is a SQL injection vulnerability in the Student Information System 1.0, specifically in the /course_edit1.php file. It occurs because the 'id' parameter received via POST requests is not properly sanitized or validated. Attackers with valid login credentials and a session cookie can inject malicious SQL code through this parameter, allowing unauthorized manipulation of database queries. This can be exploited using various SQL injection techniques such as Boolean-based blind, error-based, and time-based injections. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control by attackers, and potential disruption of service availability. This poses significant risks to system security and business continuity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in POST requests to /course_edit1.php for SQL injection using payloads such as Boolean-based blind SQL injection, error-based SQL injection, and time-based blind SQL injection. Example payloads include: - id=" RLIKE (SELECT (CASE WHEN (9300=9300) THEN '' ELSE 0x28 END))--" - id=" AND EXTRACTVALUE(6768,CONCAT(0x5c,0x717a717171,(SELECT (ELT(6768=6768,1))),0x7162626a71))--" - id=" AND (SELECT 9164 FROM (SELECT(SLEEP(5)))ndfc)--" You can use tools like curl or Burp Suite to send POST requests with these payloads while authenticated (with a valid session cookie PHPSESSID) to observe if the application behaves abnormally (e.g., delays, error messages, or unexpected responses), indicating SQL injection vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. - Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations. - Conduct regular security audits to detect and address vulnerabilities promptly. Additionally, restrict access to the vulnerable endpoint and monitor for suspicious activity until a patch is applied. [1]