CVE-2025-14514
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
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in the Campcodes Supplier Management System 1.0, specifically in the /admin/add_distributor.php file. It occurs due to improper handling of the txtDistributorAddress argument, allowing an attacker to manipulate the SQL query. 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 arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. It can compromise the confidentiality, integrity, and availability of the affected system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of CVE-2025-14514 on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized database access, data leakage, modification, and deletion, it poses significant risks to data confidentiality, integrity, and availability. Such risks could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive information. Remediation steps like input validation, use of prepared statements, and limiting database permissions are essential to maintain data security and help meet compliance requirements. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file `/admin/add_distributor.php` in the Campcodes Supplier Management System and monitoring for suspicious SQL injection attempts targeting the `txtDistributorAddress` parameter. Attackers may use Google dorking with the query `inurl:admin/add_distributor.php` to identify vulnerable targets. Network or web application firewall logs can be inspected for unusual SQL syntax or injection patterns in requests to this endpoint. Specific commands are not provided in the resources, but using web vulnerability scanners or manual testing tools to send crafted inputs to the `txtDistributorAddress` parameter can help detect the flaw. [5]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to ensure user inputs are treated strictly as data, not executable SQL code. 2) Implement strict input validation and filtering to enforce expected data formats for the `txtDistributorAddress` parameter. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as root or admin for routine database operations. 4) Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [1, 2, 5]