WordPress Plugins at Risk From Polyfill Library Compromise

Written by

WordPress plugins are currently facing significant security risks due to a recent discovery detailed in a security advisory published by Patchstack today. 

The advisory references a Polyfill supply chain attack initially reported on June 25 by Sansec. This attack targets Polyfill.js, a widely used JavaScript library that enables modern functionality on older web browsers lacking native support.

According to both companies’ findings, the attack exploits vulnerabilities in the polyfill.io domain, which Funnull, a China-based entity, recently acquired.

Malicious JavaScript code was injected into the library hosted on this domain, posing severe risks such as cross-site scripting (XSS) threats. These vulnerabilities could potentially compromise user data and redirect visitors to malicious websites, including fraudulent sports betting platforms.

Sansec’s original analysis also identified multiple compromised domains beyond polyfill.io, including bootcdn.net and bootcss.com, indicating a broader scope of affected web assets. Although immediate measures have been taken to deactivate compromised domains, residual risks persist until all affected components are thoroughly reviewed and secured.

Within the WordPress ecosystem, Patchstack’s investigation has now revealed numerous plugins and themes still integrating scripts from compromised domains. Vulnerable plugins include Amelia, WP User Frontend and Product Customer List for WooCommerce – each listed with their affected versions in the advisory.

Site administrators are strongly advised to conduct immediate audits and apply necessary updates to mitigate potential vulnerabilities.

Read more on the importance of security audits: UK Strengthens Cybersecurity Audits for Government Agencies

To enhance security further, Patchstack also recommended removing dependencies on affected domains and migrating to trusted content delivery networks (CDNs) like Cloudflare’s cdnjs.

Additionally, continuous monitoring and the implementation of content security policy (CSP) rules are crucial steps to prevent future JavaScript injection attempts and ensure robust protection against evolving cyber-threats.

Image credit: Wirestock Creators / Shutterstock.com

What’s hot on Infosecurity Magazine?