CVE-2026-2216
Path Traversal in rachelos WeRSS we-mp-rss download_export_file
Publication date: 2026-02-09
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 |
|---|---|---|
| rachelos | we-mp-rss | to 1.4.8 (inc) |
| rachelos | we_rss | to 1.4.8 (inc) |
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?
CVE-2026-2216 is a path traversal vulnerability found in the rachelos WeRSS we-mp-rss software versions up to 1.4.8. It exists in the function download_export_file within the file apis/tools.py. The flaw allows an attacker to manipulate the filename argument to traverse directories outside the intended application directory.
This means an attacker can craft specially designed requests to access and read arbitrary files on the system that should normally be restricted.
The vulnerability can be exploited remotely and does not require authentication, making it easier for attackers to gain unauthorized access to sensitive files.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information by allowing attackers to read arbitrary files on the affected system.
Since the exploit can be launched remotely without authentication, it increases the risk of data breaches and exposure of confidential data.
The impact primarily affects the confidentiality of the system, potentially exposing sensitive configuration files, credentials, or other private data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for specially crafted HTTP requests targeting the download functionality of the WeRSS application, specifically those manipulating the filename parameter to perform path traversal.'}, {'type': 'paragraph', 'content': "Network detection can involve inspecting HTTP traffic for suspicious requests containing directory traversal patterns such as '../' or encoded variants in the filename argument."}, {'type': 'paragraph', 'content': 'On the system, checking application logs for unusual access to files outside the intended directories or unexpected file download requests can help identify exploitation attempts.'}, {'type': 'list_item', 'content': "Use network monitoring tools (e.g., Wireshark, tcpdump) to filter HTTP requests with suspicious filename parameters, e.g., filtering for '../' sequences."}, {'type': 'list_item', 'content': "Example tcpdump command to capture HTTP GET requests containing '../': tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep '../'"}, {'type': 'list_item', 'content': 'Review web server or application logs for requests to the download endpoint with unusual filename parameters.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling the vulnerable download functionality in WeRSS versions up to 1.4.8 to prevent exploitation.
Since no known countermeasures or patches are available, it is recommended to replace the affected software with an alternative product that does not contain this vulnerability.
Additionally, applying network-level protections such as web application firewalls (WAFs) to block requests containing path traversal patterns in the filename parameter can reduce risk.
- Disable or restrict access to the download_export_file functionality if possible.
- Implement input validation or filtering at the application or proxy level to block path traversal sequences.
- Monitor and block suspicious HTTP requests with directory traversal attempts.
- Plan to upgrade or replace the vulnerable WeRSS software with a secure alternative.