Swfupload – Security Threat (2016)
-
RE: root/wp-includes/js/swfupload/
I had 2 of my client WordPress sites hacked in this past month and they uploaded malicious PHP and JS files to infect the site with a backdoor PHP script. When I found the hacked upload 2 weeks ago in one client’s site, I wondered how did they got into the site while using WordFence Premium?
Now I think I found the hackers method, I believe they used “swfupload”.
Any security scan will not show “swfupload” as a danger because WordPress (foolishly) includes these script files for legacy reasons. Apart from that, the files in folder “swfupload” are not needed for current WordPress installs. These are old files and since they are old they are NO longer updated to stop hackers.
Now that I had 2 client websites hacked and malicious files uploaded, I believe that is the weak spot in WordPress allowing the hacker to gain access.
Why do I post this string?
To tell WordPress to STOP including that damn folder and files. Its over 7 yrs of legacy inclusion and its time to end it.
All WordPress users need to remove that folder and contents and yes, if you have plugin that depends on it, contact the plugin author to get their butts in gear to stop using that vulnerability.
Unfortunately, since WordPress Dev’s still include it, that means each time WordPress is updated, you need to access your folder/file system via SFTP and delete that folder.
I am going to notify WordFence to include that folder as a warning as the default setting.
… and No, any suggested mod to those old files to keep the old swfupload is not a good idea. Hackers are far more intelligent to overcome that than any of us.
Removing the entire folder is the best move.
- The topic ‘Swfupload – Security Threat (2016)’ is closed to new replies.