CVE-2025-10025
BaseFortify
Publication date: 2025-09-05
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-10025 is a critical SQL injection vulnerability in the PHPGurukul Online Course Registration version 3.1, specifically in the /admin/semester.php file. The vulnerability occurs because the 'semester' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially leading to unauthorized access, data leakage, modification, deletion, or disruption of the system. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data. It can also cause disruption of service and potentially full system compromise. Since the attack can be performed remotely without authentication, it poses a severe risk to system security, data integrity, and business continuity. [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 'semester' parameter in POST requests to the /admin/semester.php file for SQL injection. A time-based blind SQL injection test can be performed by sending a payload such as: semester=132' AND (SELECT 3975 FROM (SELECT(SLEEP(5)))gkJG) AND 'gmpP'='gmpP. If the response is delayed by the sleep time, it confirms the injection point. Additionally, scanning for the presence of the vulnerable endpoint using Google dorking with the query inurl:admin/semester.php can help identify targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'semester' parameter to ensure it conforms to expected formats, and minimizing database user permissions by avoiding the use of high-privilege accounts for routine database operations. If possible, replacing the affected component with an alternative product is also suggested. [2, 3, 1]