CVE-2025-14952
BaseFortify
Publication date: 2025-12-19
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14952 is a critical SQL injection vulnerability in Campcodes Supplier Management System version 1.0, specifically in the file /admin/add_category.php. It occurs because the txtCategoryName parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data modification or deletion, full system compromise, and potential service disruption. Since no authentication is required, attackers can remotely exploit this flaw to compromise the confidentiality, integrity, and availability of the system and its 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 testing the vulnerable parameter 'txtCategoryName' in the file /admin/add_category.php for SQL injection. A demonstrated method is using a time-based blind SQL injection payload such as: txtCategoryName=123' AND (SELECT 5492 FROM (SELECT(SLEEP(5)))CUBX) AND 'GcNW'='GcNW which causes a delay in the database response, confirming the injection point. Additionally, the sqlmap tool can be used to detect the vulnerability with a command like: sqlmap -u "http://<target>/Supply_Management_System/admin/add_category.php" --data="txtCategoryName=123&txtCategoryDetails=123" --dbs. Vulnerable targets can also be identified using Google dorking with queries like inurl:admin/add_category.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for application database connections. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected product or component with a secure version. [1, 2]
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 database access, data leakage, modification, or deletion, it could potentially lead to violations of data protection and privacy regulations by compromising confidentiality, integrity, and availability of sensitive data. Organizations using the affected system may face compliance risks if personal or sensitive data is exposed or altered due to this SQL injection vulnerability. [1, 2, 3]