Sergey Nivens - Fotolia

News Stay informed about the latest enterprise technology news and product updates.

How the WordPress XSS vulnerability was patched so quickly

WordPress was found to have two new zero-day XSS vulnerabilities that were being exploited, but a patch has already been issued to mitigate the issues.

Two new zero-day WordPress XSS vulnerabilities have been found to be targeted by attacks in the wild, but WordPress has worked quickly to issue a patch and fix the issues.

David Dede, a malware researcher with Sucuri Inc., wrote about vulnerabilities in at least two WordPress plug-ins that could lead to XSS exploits. One plug-in the TwentyFifteen theme is installed by default and the other is JetPack, a popular customization and performance plug-in that has more than one million active installs.

Dede said more plug-ins could well have been vulnerable because the root cause was the genericons package, a WordPress add-on that provides icons that are commonly used in WordPress site templates. The font itself wasn't the issue; the problem instead stemed from a file demonstrating potential uses. Any plug-in that included this example.html file could be vulnerable. His post also noted that the Sucuri team detected attacks on this vulnerability in the wild "days before disclosure."

The XSS vulnerability in this package could be leveraged with an exploit at the Document Object Model level, according to Dede, meaning that it could be executed directly in the browser. Dede noted that this type of attack is usually more difficult to exploit and harder to block, but the fix in this case was relatively straightforward.

Dede said that simply deleting the example.html file from the genericons directory, or using a Web application firewall or IPS to block access to that file, would remove the vulnerability.

Additionally, the WordPress 4.2.2 update has been released to fix this issue as well as a separate XSS vulnerability that had affected versions 4.2 and lower. The update will scan a site's directory and remove the vulnerable HTML file.

The WordPress blog post also said all affected themes and plug-ins hosted at WordPress.org have been updated to remove the vulnerable file.

Robert Graham, CEO of Atlanta-based Errata Security, said that the specific files that were vulnerable and attack vector aren't very important, because the WordPress ecosystem is inherently insecure.

"WordPress is a horribly complex system that is full of holes," said Graham. "If you see a WordPress site, you know it's probably able to be hacked. It's an inherent danger, and you have to keep up with patches aggressively. I don't know that the patching process is something that most places have the resources to do."

Ultimately, Graham suggested enterprises may be better served using WordPress.com, for the automatic updates, or another blogging platform entirely because of the constant security flaws in WordPress.

Next Steps

Learn how to run a secure WordPress installation in an IaaS VM.

Dig Deeper on Web application and API security best practices

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

Does your organization run WordPress? How do you handle security for it?
Cancel

-ADS BY GOOGLE

SearchCloudSecurity

SearchNetworking

SearchCIO

SearchEnterpriseDesktop

SearchCloudComputing

ComputerWeekly.com

Close