CVE-2025-9729
BaseFortify
Publication date: 2025-08-31
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 |
|---|---|---|
| phpgurukul | online_course_registration | 3.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9729 is a critical SQL injection vulnerability in the PHPGurukul Online Course Registration version 3.1, specifically in the /admin/student-registration.php file. The vulnerability occurs because the 'studentname' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of SQL queries, potentially allowing attackers to access, modify, or delete sensitive data in the database remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can view, modify, or delete sensitive information stored in the database. Since the attack can be performed remotely without authentication, it poses a significant security risk to the affected system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "studentname" parameter in the /admin/student-registration.php file for SQL injection. A common method is to use a time-based blind SQL injection payload such as: studentname=111' AND (SELECT 8651 FROM (SELECT(SLEEP(5)))ledK) AND 'YcaO'='YcaO which causes a delay in the database response if vulnerable. Tools like sqlmap can be used to automate detection and enumeration of databases. Additionally, searching for the vulnerable URL using Google dorking (e.g., inurl:admin/student-registration.php) can help identify exposed targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. If possible, replace the affected software with an alternative product. These measures help protect system security and maintain data integrity. [2, 3]