CVE-2025-14885
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 |
|---|---|---|
| lerouxyxchire | client_database_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14885 is a critical vulnerability in SourceCodester Client Database Management System version 1.0, specifically in the Leads Generation module's /user_leads.php file. It allows attackers to perform unrestricted file uploads without proper server-side validation, enabling them to upload malicious executable files such as PHP scripts. These files are stored in a publicly accessible directory with directory listing enabled, allowing attackers to execute arbitrary code remotely on the server. This can lead to full system compromise including remote code execution, privilege escalation, data theft, and destruction. [1, 2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to severe impacts including remote command execution on the server, deployment of web shells, theft of database credentials, privilege escalation, data exfiltration or destruction, and ultimately full compromise of the affected system. The vulnerability affects the confidentiality, integrity, and availability of the system and can be exploited remotely with minimal effort. [1, 2]
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 uploaded executable files in the web-accessible directory /cdm/files/, especially files with extensions like .php, .phtml, or .php5. Directory listing enabled on this folder can facilitate detection. Additionally, scanning web server logs for requests to /cdm/user_leads.php that include file upload activity or suspicious file names can help. Using Google dorking with the query inurl:user_leads.php can identify vulnerable targets externally. Commands to detect suspicious files might include: 1) Listing files with executable extensions: `ls -l /path/to/cdm/files/*.php` 2) Searching web server access logs for upload attempts: `grep 'user_leads.php' /var/log/apache2/access.log | grep -i 'upload'` 3) Checking for directory listing enabled: `curl -I http://yourserver/cdm/files/` and look for 'Options -Indexes' absence. 4) Using find to locate recently uploaded executable files: `find /path/to/cdm/files/ -type f \( -name '*.php' -o -name '*.phtml' -o -name '*.php5' \) -mtime -7` to find files uploaded in the last 7 days. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Blocking executable file extensions (.php, .phtml, .php5, etc.) from being uploaded. 2) Implementing server-side validation of file types and MIME types to allow only safe file formats (e.g., PDF, JPG, PNG). 3) Disabling directory listing on the /cdm/files/ directory (e.g., by setting 'Options -Indexes' in the web server configuration). 4) Storing uploaded files outside the web root to prevent direct web access. 5) Renaming uploaded files with random UUIDs to prevent predictable access. 6) Serving uploaded files via a download handler rather than direct URL access. 7) Enforcing least privilege permissions on upload directories. 8) Adding Web Application Firewall (WAF) rules to detect and block file upload abuse. If immediate patching or fixing is not possible, consider replacing the affected component with an alternative product as no known countermeasures are currently available. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows remote attackers to upload and execute arbitrary files, leading to potential full system compromise, data exfiltration, and unauthorized access to sensitive information. Such impacts can result in violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches. The lack of proper file validation and security controls increases the risk of non-compliance with these standards due to potential data confidentiality, integrity, and availability breaches. [1, 2]