CVE-2025-14589
BaseFortify
Publication date: 2025-12-13
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 |
|---|---|---|
| carmelo | prison_management_system | 2.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 SQL injection issue in the Prison Management System 2.0, specifically in the /admin/search.php file. By manipulating the 'keyname' argument, an attacker can inject malicious SQL code. The attack can be performed remotely and the exploit is publicly available.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute unauthorized SQL commands on the database, potentially leading to data leakage, data modification, or disruption of the system's normal operation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to gain unauthorized access to sensitive personal data such as full names, student IDs, national identification numbers, grades, and home addresses. This unauthorized access and potential data breach could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. The compromise of confidentiality, integrity, and availability of data due to this SQL injection flaw poses significant risks to compliance with these standards. [1, 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 /admin/search.php endpoint for SQL injection via the 'keyname' parameter. One approach is to send crafted HTTP requests with SQL injection payloads such as single quotes (') or UNION-based queries to observe if the system returns SQL errors or unexpected data. Additionally, Google dorking can be used to identify vulnerable targets by searching for "inurl:admin/search.php". Example commands include using curl to send test payloads: curl -G 'http://target/admin/search.php' --data-urlencode "keyname=' OR '1'='1" or using sqlmap to automate detection: sqlmap -u "http://target/admin/search.php?keyname=test" --risk=3 --level=5. Monitoring network traffic for unusual SQL queries or error messages related to this endpoint can also help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known mitigations or countermeasures have been documented. Additionally, restricting access to the /admin/search.php endpoint to trusted users or IP addresses can reduce exposure. Applying web application firewalls (WAF) rules to detect and block SQL injection attempts targeting the 'keyname' parameter may help temporarily. Ultimately, updating or patching the software to fix the improper handling of the 'keyname' parameter by implementing input validation, sanitization, or parameterized queries is necessary to fully mitigate the vulnerability. [1, 3]