CVE-2025-14530
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 |
|---|---|---|
| remyandrade | real_estate_property_listing_app | 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
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 upload functionality in /admin/property.php of the SourceCodester Real Estate Property Listing App. One method is to look for signs of arbitrary file uploads, such as unexpected PHP files in the upload directory. Additionally, attackers may use Google dorking with the query "inurl:admin/property.php" to identify vulnerable targets. To detect exploitation attempts on your system, you can search your web server logs for POST requests to /admin/property.php with the "image" parameter containing suspicious file uploads. Example commands to detect suspicious files or activity include: 1) Searching for PHP files in the upload directory: `find /path/to/upload/directory -name '*.php'` 2) Checking web server logs for suspicious POST requests: `grep 'POST /admin/property.php' /var/log/apache2/access.log | grep 'image='` 3) Using Google dorking externally to find exposed admin pages: `site:yourdomain.com inurl:admin/property.php` These steps help identify if the vulnerability is present and if exploitation attempts have occurred. [2, 3]
Can you explain this vulnerability to me?
This vulnerability exists in the SourceCodester Real Estate Property Listing App 1.0, specifically in an unknown function within the file /admin/property.php. It involves manipulation of the 'image' argument, which leads to unrestricted file upload. This means an attacker can remotely upload files without proper restrictions, potentially allowing malicious files to be placed on the server.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely upload arbitrary files to the server, which can lead to unauthorized access, data modification, or denial of service. This could compromise the integrity, confidentiality, and availability of the affected system.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing strict server-side validation of file uploads to allow only safe image formats such as JPG and PNG. Enforce a whitelist of allowed file extensions and reject all others. Disable execution permissions in the upload directory to prevent execution of uploaded scripts. Sanitize file names to prevent injection of malicious code. If possible, restrict access to the /admin/property.php file to trusted users only and monitor for suspicious activity. Consider replacing or patching the vulnerable component. These measures reduce the risk of arbitrary file upload and remote code execution. [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 the vulnerable file upload functionality in /admin/property.php and monitoring for suspicious file uploads via the 'image' parameter. One detection method is to look for uploaded files with unexpected extensions (e.g., .php) in the upload directory. Additionally, attackers may use Google dorking with the query 'inurl:admin/property.php' to identify vulnerable targets. Commands to detect suspicious files could include: 1) On the server, list files with PHP extensions in the upload directory, e.g., `find /path/to/uploads -type f -name '*.php'` 2) Check web server logs for POST requests to /admin/property.php containing the 'image' parameter, e.g., `grep 'POST /admin/property.php' /var/log/apache2/access.log | grep image` 3) Use network monitoring tools to detect unusual file upload activity targeting /admin/property.php. These steps help identify exploitation attempts or presence of uploaded web shells. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement strict server-side validation to whitelist only allowed image file types such as JPG and PNG for the 'image' parameter uploads. 2) Disable execution permissions in the upload directory to prevent execution of uploaded scripts. 3) Sanitize and validate file names to prevent malicious payloads. 4) Restrict access to the /admin/property.php interface to authorized users only and monitor for suspicious activity. 5) If possible, replace or update the vulnerable component to a secure version or alternative product. These measures reduce the risk of arbitrary file upload and remote code execution. [2]