CVE-2025-14877
BaseFortify
Publication date: 2025-12-18
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, modification, and deletion of sensitive data due to SQL injection, which can lead to breaches of confidentiality, integrity, and availability of data. Such breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA that require protection of sensitive information and data integrity. Therefore, this vulnerability poses a significant risk to compliance with these regulations if exploited. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-14877 is a critical SQL injection vulnerability in Campcodes Supplier Management System version 1.0, specifically in the /admin/add_retailer.php file. The vulnerability occurs because the 'cmbAreaCode' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, leak sensitive information, modify or delete data, and potentially take full control of the system. It can also disrupt service availability, compromising the confidentiality, integrity, and availability of your system and data. [1, 2, 3]
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_retailer.php and testing the cmbAreaCode parameter for SQL injection. One method is to use Google dorking with queries like "inurl:admin/add_retailer.php" to identify potentially vulnerable targets. Additionally, manual testing or automated scanning tools can be used to inject SQL payloads into the cmbAreaCode parameter to observe if the system is vulnerable. Specific commands are not provided, but using tools like curl or sqlmap targeting the cmbAreaCode parameter in the URL or POST data can help detect the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Implementing prepared statements or parameterized queries to ensure user inputs like cmbAreaCode are treated strictly as data, not executable SQL code. 3) Applying strict input validation and filtering to ensure inputs conform to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 5) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. [2, 3]