CVE-2025-11557
BaseFortify
Publication date: 2025-10-09
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 |
|---|---|---|
| projectworlds | gate_pass_management_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?
This vulnerability is a critical SQL injection flaw in the Gate Pass Management System 1.0, specifically in the /add-pass.php file. It occurs because the 'fullname' parameter is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of the database through crafted input. [1, 2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow attackers to gain unauthorized access to the database, read sensitive data, modify or delete records, and potentially take full control of the system or disrupt its services. This severely compromises system security and business continuity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /add-pass.php endpoint for SQL injection via the 'fullname' parameter. You can use tools like curl or sqlmap to test for SQL injection. For example, using curl: curl -X POST -d "fullname=1' OR '1'='1&contactno=8787451200&email=1%40qq.com&idtype=Voter+Card&idcardno=1&category=Visitor&fromdate=2025-01-01&todate=2025-01-01&reason=1&submit=" http://targetsite/add-pass.php. Alternatively, sqlmap can be used to automate detection: sqlmap -u "http://targetsite/add-pass.php" --data="fullname=1&contactno=8787451200&email=1%40qq.com&idtype=Voter+Card&idcardno=1&category=Visitor&fromdate=2025-01-01&todate=2025-01-01&reason=1&submit=" -p fullname --batch. Monitoring network traffic for suspicious SQL injection payloads targeting /add-pass.php can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding in the /add-pass.php code to prevent SQL injection. 2) Apply strict input validation and filtering on the 'fullname' parameter to ensure only expected data formats are accepted. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine database operations. 4) Conduct a thorough security audit of the application code and system to identify and fix other potential vulnerabilities. These steps will help prevent exploitation and secure the system. [1]