CVE-2025-5562
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 | curfew_e-pass_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?
This vulnerability is a critical SQL injection flaw in the Curfew e-Pass Management System 1.0, specifically in the /admin/edit-category-detail.php file. It 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, potentially gaining unauthorized access to the database, extracting or modifying data, and even taking full control of the system. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control by attackers, and potential disruption of services. Exploitation techniques include Boolean-based, time-based, stacked queries, and UNION-based SQL injection, which can severely compromise 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 'editid' parameter in the /admin/edit-category-detail.php file for SQL injection. You can use SQL injection payloads such as boolean-based, time-based, or UNION-based injections. For example, using sqlmap targeting the 'editid' parameter is a demonstrated proof of concept. Sample payloads include: - Boolean-based: editid=4 AND 6325=6325 - Time-based: editid=4 AND (SELECT 7212 FROM (SELECT(SLEEP(5)))bzdA) - UNION-based: editid=4 UNION ALL SELECT NULL,CONCAT(0x7176767871,0x676d446c726a69504d524f65636841435a4e47414c6d5252747551626a4e74466d71495671527168,0x7162787171),NULL-- - Using sqlmap command example: sqlmap -u "http://targetsite/admin/edit-category-detail.php?editid=4" --batch --dbs [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. - Enforce strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user privileges by avoiding high-privilege accounts for routine operations. These steps help prevent SQL injection attacks and reduce the risk of unauthorized database access and data tampering. [1]