CVE-2025-5556
BaseFortify
Publication date: 2025-06-04
Last updated on: 2025-06-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | teacher_subject_allocation_management_system | 1.0 |
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-5556 is a critical SQL injection vulnerability in PHPGurukul Teacher Subject Allocation Management System version 1.0, specifically in the /admin/edit-teacher-info.php file. The vulnerability occurs because the 'editid' parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, which can manipulate the database, leading to unauthorized access or modification of data. [1, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. Attackers can exploit it remotely to access sensitive data, manipulate or delete database records, and potentially disrupt services. It can lead to unauthorized database access, data leakage, data manipulation, and even full system compromise or service disruption. [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 'editid' parameter in the /admin/edit-teacher-info.php file for SQL injection. Tools like sqlmap can be used to automate detection. Example commands include using sqlmap to test the parameter: sqlmap -u "http://target/admin/edit-teacher-info.php?editid=1" --batch. Additionally, manual testing with payloads such as 'editid=4 AND 1023=1023', 'editid=4;SELECT SLEEP(5)#', or 'editid=4 AND (SELECT 9077 FROM (SELECT(SLEEP(5)))ApVj)' can help identify time-based or boolean-based SQL injection. Google dorking with queries like 'inurl:admin/edit-teacher-info.php' can help identify vulnerable 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 'editid' parameter, and restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Since no known countermeasures or patches are currently available, replacing the affected product with a secure alternative is also suggested. [2, 3]