16 May 2023

Akamai SIG’s Advanced Custom Fields (ACF) Attack Claim Confuses Script Kiddie With Attacker

In the past couple of days there have been scary sounding claims from journalists related to a recently fixed reflected cross-site scripting (XSS) vulnerability in the WordPress plugin Advanced Custom Fields (ACF), which we had detailed on May 4 after a machine learning (AI) based system we have flagged the fix being made. The journalists claimed that an attacker was trying to exploit this. With headline claims including, “Hackers target WordPress plugin flaw after PoC exploit released” from the Bleeping Computer, as well as “Hackers exploit WordPress vulnerability within hours of PoC exploit release” from CSO Online, and “ACF Plugin’s Reflected XSS Vulnerability Attracts Exploit Attempts Within 24 Hours of Public Announcement” from the WP Tavern.

Those stories are somewhat inaccurate, as they are citing another company’s disclosure a day after us as being when the vulnerability was disclosed. But the far larger issue is that it seemed highly unlikely that an attacker was really trying to exploit this. If this was true, it would be rather news worthy since we have seen no evidence of any wide scale exploitation of reflected XSS vulnerabilities in WordPress plugins. It turns out the source for those stories, Akamai Security Intelligence Group (SIG) confused a script kiddie with an attacker, leading to those misleading stories. [Read more]

8 Apr 2016

Before You Blame A Hack on a WordPress Plugin, There Should Be Evidence That a Hack Actually Happened

One of the things we do to make sure we are staying on top of security issues in WordPress plugins in keep track on any news stories mentioning them. That leads us to seeing a lot of really bad journalism, like this article at CSO Online where it was claimed that the LA Times website was hacked without the evidence needed to back this up, much less that it was due to a vulnerability in a WordPress plugin.

When we first came across this we were fairly concerned since the article claimed an older vulnerability in the Advanced XML Reader plugin, which we didn’t have in our data set, was possibly used to exploit the website. [Read more]