CVE-2025-48130
BaseFortify
Publication date: 2025-06-09
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Path Traversal issue in the WordPress Spice Blocks plugin (up to version 2.0.7.2) that allows unauthenticated attackers to download arbitrary files from the affected website. This means attackers can access sensitive files outside the intended restricted directories, potentially exposing confidential data such as login credentials and backup files. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized disclosure of sensitive information by allowing attackers to download arbitrary files from your website without authentication. This can expose critical data like login credentials and backups, increasing the risk of further attacks or data breaches. Since no official patch is available, immediate mitigation using virtual patches is recommended to protect your site. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for exploit attempts targeting the arbitrary file download flaw in Spice Blocks plugin versions up to 2.0.7.2. Since the exploit requires no authentication and allows downloading arbitrary files, network detection can focus on unusual HTTP requests attempting to access sensitive files or paths outside the intended directory. Specific commands are not provided in the resources, but general approaches include inspecting web server logs for suspicious path traversal patterns (e.g., '../' sequences) and using server-side malware scanning as recommended. Plugin-based malware scanners may be unreliable due to tampering, so professional incident response and server-side scanning are advised. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the virtual patch (vPatch) provided by Patchstack, which blocks exploit attempts until an official fix is released. This virtual patch can be safely applied and tested to protect affected websites immediately. Additionally, website owners should consider professional incident response and server-side malware scanning if a compromise is suspected. Since no official patch or fixed version is currently available, relying on the virtual patch and monitoring for exploitation attempts are critical. [1]