CVE-2025-5873
BaseFortify
Publication date: 2025-06-09
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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-5873 is an unrestricted file upload vulnerability in the eCharge Hardy Barth Salia PLCC version 2.2.0 Web UI, specifically in the /firmware.php file. It occurs due to improper handling of the 'media' argument, allowing an attacker to upload arbitrary files, including malicious scripts. This can lead to remote code execution, giving the attacker full control over the affected system. [1, 2]
How can this vulnerability impact me? :
Exploiting this vulnerability can compromise the confidentiality, integrity, and availability of the affected system. An attacker can remotely upload malicious files to gain arbitrary remote command execution, potentially taking full control of the device. The attack requires no authentication and can be performed remotely, making it highly accessible and dangerous. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the presence of the vulnerable endpoint /firmware.php on your system or network. Google Hacking techniques such as searching for "inurl:firmware.php" can help identify vulnerable targets. Additionally, monitoring HTTP requests for uploads to /firmware.php with the "media" argument may indicate exploitation attempts. Specific commands are not provided, but using tools like curl or wget to test file upload functionality on /firmware.php could help detect the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
No official mitigations or patches are available for this vulnerability. Immediate steps include replacing the affected product with an alternative solution. Additionally, restricting access to the /firmware.php endpoint, implementing network-level controls to block suspicious upload attempts, and monitoring for exploitation activity are recommended to reduce risk until a patch or fix is available. [2]