CVE-2025-10246
BaseFortify
Publication date: 2025-09-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 |
|---|---|---|
| lokibhardwaj | php-code-for-unlimited-file-upload | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Scripting (XSS) issue in the PHP project "PHP-Code-For-Unlimited-File-Upload" by lokibhardwaj. It occurs in the file /f.php where the value of the POST parameter 'h' is directly output into a hidden input field without proper sanitization or encoding. This allows an attacker to inject malicious scripts that can be executed in the context of the victim's browser, leading to potential script-based attacks. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to inject malicious scripts into the affected web application, which can then be executed in the browsers of users who visit the vulnerable page. This can lead to unauthorized actions such as session hijacking, defacement, or redirection to malicious sites. Remote exploitation is possible but requires user interaction. The integrity of the system is impacted due to the injection of unauthorized scripts. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying the presence of the vulnerable file `f.php` in the PHP-Code-For-Unlimited-File-Upload project and checking if it improperly handles the `h` parameter. One method to find potentially vulnerable targets is using Google dorking with the query `inurl:f.php`. Additionally, inspecting HTTP POST requests to `f.php` for the `h` parameter and analyzing the response for reflected or stored scripts can help detect exploitation attempts. Specific commands for detection are not provided in the resources. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component with an alternative product, as no known countermeasures or patches have been published. Avoid using the vulnerable version up to commit `124fe96324915490c81eaf7db3234b0b4e4bab3c`. Additionally, implementing input sanitization and output encoding for the `h` parameter in `f.php` can prevent script injection. Since the vendor has not responded and no official fixes exist, removing or disabling the vulnerable functionality is recommended. [2]