CVE-2025-9937
BaseFortify
Publication date: 2025-09-04
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 |
|---|---|---|
| elunez | eladmin | 1.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-266 | A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. |
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9937 is a Broken Function Level Authorization vulnerability in elunez eladmin 1.1, specifically in the deleteFile method of the LocalStorageController. It allows a low-privileged user with the "storage:del" permission to delete files owned by other users because the system only checks for the permission but does not verify file ownership. The exploit involves sending a DELETE request with file IDs to delete files arbitrarily, leading to unauthorized file deletion. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to arbitrary deletion of files by unauthorized users, resulting in potential data loss and denial of service. It compromises the integrity and availability of the affected system, as attackers can delete files they do not own remotely without proper authorization. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unauthorized DELETE requests to the /api/localStorage endpoint, especially those containing JSON arrays of file IDs for deletion. Network traffic analysis tools or web application firewalls can be used to detect such suspicious requests. Specific commands are not provided in the resources, but inspecting HTTP DELETE requests targeting /api/localStorage with tools like curl or using network monitoring tools to log such requests may help identify exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /api/localStorage deleteFile function, monitoring and blocking unauthorized DELETE requests, and considering replacing the affected component with an alternative product as no known countermeasures or patches are documented. Applying strict access controls and limiting permissions to trusted users may reduce risk until a fix is available. [2]