CVE-2015-10144
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-12-16
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| i13websolution | thumbnail_carousel_slider | to 1.0.1 (inc) |
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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the WordPress Responsive Thumbnail Slider plugin (versions up to 1.0.1) and allows authenticated users with subscriber-level access or higher to upload arbitrary files due to missing file type sanitization in the image uploader. Attackers can upload files with double extensions (e.g., shell.php.jpg) and then rename them to executable files (e.g., shell.php), enabling them to upload malicious PHP shells disguised as images. This can lead to remote code execution on the affected server. [1, 2, 4]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to upload and execute malicious code on the server hosting the WordPress site. This can lead to unauthorized remote code execution, full website compromise, privilege escalation, unauthorized access, and potential control over the server. The attacker can run arbitrary commands, potentially leading to data theft, site defacement, or further attacks on the infrastructure. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by checking if the vulnerable Responsive Thumbnail Slider plugin version 1.0 or earlier is installed on your WordPress site. You can verify the plugin version by fetching and inspecting the file /wp-content/plugins/wp-responsive-thumbnail-slider/readme.txt. Additionally, check for the existence of the upload directory /wp-content/uploads/wp-responsive-images-thumbnail-slider/. Monitoring for suspicious file uploads with double extensions (e.g., shell.php.jpg) in this directory is also recommended. Using tools like Burp Suite or Tamper Data to intercept and analyze file upload requests to the plugin's image upload section can help detect exploitation attempts. There is also a Metasploit module that automates version checking and exploitation, which can be used to verify vulnerability presence. Example commands include: 1. Check plugin version: curl -s https://yourwordpresssite.com/wp-content/plugins/wp-responsive-thumbnail-slider/readme.txt | grep "Stable tag" 2. Check upload directory existence: curl -I https://yourwordpresssite.com/wp-content/uploads/wp-responsive-images-thumbnail-slider/ 3. Monitor web server logs for uploads with double extensions like *.php.jpg 4. Use Burp Suite or similar proxy tools to intercept and analyze POST requests to wp-admin/admin.php?page=responsive_thumbnail_slider_image_management 5. Optionally, use the Metasploit module to verify vulnerability by running the auxiliary scanner or exploit module with valid credentials. [1, 2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or uninstalling the Responsive Thumbnail Slider plugin until a patched version is available. Restricting file upload permissions and access to the plugin's image upload functionality to trusted users only can reduce risk. Implementing proper file type validation and sanitization on the server side to prevent arbitrary file uploads is critical. Monitoring and removing any suspicious files uploaded to the server, especially those with double extensions, is advised. Applying the latest security patches or updates from the plugin developer once available is recommended. If possible, restrict authenticated user roles to prevent subscriber-level users from uploading files. As a temporary measure, consider using web application firewalls (WAF) to block malicious upload attempts targeting this plugin. [3]