a3 Lazy Load <= 2.6.0 - Cross-Site Request Forgery to Settings Reset
Strategic Overview
- Status
- Patched in 2.6.1
- Affected Plugin
- a3 Lazy Load
- Affected Version
<= 2.6.0- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the a3 Lazy Load WordPress plugin, affecting versions <= 2.6.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.6.1; sites on affected versions should update now. Disclosed November 2022.
Vulnerability Overview
The following plugins for WordPress are vulnerable to Cross-Site Request Forgery: a3 Lazy Load (<= 2.6.0), Contact Us Page – Contact People (<= 3.6.1), a3 Portfolio (<= 3.0.1), Dynamic Product Gallery for WooCommerce (3.0.1), a3 Responsive Slider (<= 2.2.0), Compare Products for WooCommerce (<= 2.8.2), Products Quick View for WooCommerce (<= 2.0.1), Product Sort and Display for WooCommerce (<= 2.2.2), Product Widget Slider for WooCommerce (), WP Email Template (<= 2.6.2). This is due to missing nonce validation on the reset_settings() function. This makes it possible for unauthenticated attackers to reset the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
a3 Lazy Load <= 2.6.0 carries this weakness at reset_settings(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For a3 Lazy Load the fix is 2.6.1: builds <= 2.6.0 are affected, anything from 2.6.1 onward is not.
Remediation
Update to version 2.6.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to a3 Lazy Load: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: a3 Lazy Load 2.6.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C