CVE-2025-10083
BaseFortify
Publication date: 2025-09-08
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 |
|---|---|---|
| mayuri_k | pet_grooming_management_software | 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-10083 is an unrestricted file upload vulnerability in SourceCodester Pet Grooming Management Software version 1.0, specifically in the profile image upload functionality within the /admin/profile.php file. Due to insufficient server-side validation and filtering, attackers with valid credentials can upload malicious files such as PHP webshells. These files are saved directly with their original filenames into a web-accessible directory without sanitization, allowing attackers to access and execute arbitrary code on the server remotely. [1, 2, 3, 5]
How can this vulnerability impact me? :
This vulnerability can lead to full remote code execution on the affected server, resulting in complete compromise of the web application. Attackers can escalate privileges, move laterally within the network, dump databases, steal credentials, tamper with content, disable the application, leak user privacy, and ultimately take over the entire server. [1, 2, 3, 5]
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 suspicious or unauthorized PHP files uploaded in the web-accessible directory `/petgrooming_erp/pet_grooming/assets/uploadImage/Profile/`. You can look for files with PHP extensions such as `.php` that should not normally be present in an image upload folder. Additionally, monitoring web server logs for access to such files or unusual query parameters (e.g., `?cmd=`) can help identify exploitation attempts. Suggested commands include: 1) Listing suspicious files: `find /path/to/webroot/petgrooming_erp/pet_grooming/assets/uploadImage/Profile/ -type f -name '*.php'` 2) Checking recent uploads: `ls -lt /path/to/webroot/petgrooming_erp/pet_grooming/assets/uploadImage/Profile/` 3) Searching web server logs for access to uploaded PHP files: `grep 'shell.php' /var/log/apache2/access.log` or similar log files. 4) Using network monitoring tools to detect unusual HTTP requests targeting `/admin/profile.php` or uploaded PHP files. These steps help detect if the vulnerability has been exploited or if malicious files exist on the system. [2, 3, 5]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Restrict file uploads to only safe image formats such as `.png`, `.jpg`, and `.jpeg` by implementing server-side validation of MIME types and file extensions. 2) Sanitize and rename uploaded files to prevent execution of arbitrary code and avoid using original filenames. 3) Store uploaded files outside the webroot or in directories configured to prevent execution of scripts. 4) Configure the web server to disable execution of scripts in the upload directory (e.g., using `.htaccess` or server configuration). 5) Monitor upload activities and maintain logs including time, IP address, user, and filename to detect suspicious behavior. 6) If possible, apply patches or updates from the vendor or replace the affected software with a secure alternative. 7) Limit user privileges to reduce the risk of authenticated attackers exploiting the vulnerability. These steps help prevent attackers from uploading and executing malicious scripts via the vulnerable profile image upload functionality. [2, 3, 5]