CVE-2025-14515
BaseFortify
Publication date: 2025-12-11
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 |
|---|---|---|
| campcodes | supplier_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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access to the underlying database, enabling attackers to retrieve, modify, or delete sensitive information. Such unauthorized data access and potential data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data. Therefore, if exploited, this vulnerability could result in violations of these standards due to compromised confidentiality, integrity, and availability of data. [2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable URL /admin/add_unit.php for SQL injection in the txtunitDetails parameter. A proof-of-concept uses a time-based blind SQL injection payload such as: txtUnitName=jone&txtunitDetails=123' AND (SELECT 8822 FROM (SELECT(SLEEP(5)))qqcP) AND 'zNOO'='zNOO which causes a delay in the response if vulnerable. Tools like sqlmap can be used to automate detection by targeting the vulnerable URL with the parameter txtunitDetails. Additionally, Google dorking with queries like inurl:admin/add_unit.php can help identify potentially vulnerable targets on your network or externally. [3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the txtunitDetails parameter to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product to avoid exploitation. These steps help secure the system and maintain data integrity. [3, 4]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access, modification, and leakage of sensitive data through SQL injection, it could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive information. Organizations using the affected system should consider this risk and take immediate remediation steps to maintain compliance. [2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable URL /admin/add_unit.php for SQL injection in the txtunitDetails parameter. A proof-of-concept time-based blind SQL injection payload is: txtUnitName=jone&txtunitDetails=123' AND (SELECT 8822 FROM (SELECT(SLEEP(5)))qqcP) AND 'zNOO'='zNOO. Using tools like sqlmap targeting the URL can automate detection. Additionally, Google dorking with queries such as inurl:admin/add_unit.php can help identify potentially vulnerable targets. [3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product to avoid exploitation. [3, 4]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue in the Campcodes Supplier Management System 1.0, specifically in the /admin/add_unit.php file. It occurs due to manipulation of the txtunitDetails argument, allowing an attacker to inject malicious SQL code remotely.
How can this vulnerability impact me? :
The 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.