a3rev Multiple Plugins <= Various Versions - Cross-Site Request Forgery to Settings Changes
Strategic Overview
- Status
- Patched in 2.5.0
- Affected Plugin
- a3 Lazy Load
- Affected Version
<= 2.4.9- 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.4.9. 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.5.0; sites on affected versions should update now. Disclosed May 2022.
Vulnerability Overview
The a3 Lazy Load, a3 Portfolio, Contact Us Page – Contact People, Dynamic Product Gallery for WooCommerce, a3 Responsive Slider, and Compare Products for WooCommerce plugins for WordPress are vulnerable to Cross-Site Request Forgery respectively in versions up to, and including, 2.5.0, 3.0.0, 3.6.0, 2.9.0, 2.0.12, 2.8.0. This is due to missing nonce validation on the save_settings function present in all three plugins. This makes it possible for unauthenticated attackers to to update the plugins settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. It is also worth noting that there were several additional changes in the plugins related to sanitization and escaping so there may be other vulnerabilities that were fixed as part of these releases.
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)
Reaching this weakness in a3 Lazy Load <= 2.4.9 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.5.0: builds <= 2.4.9 are affected, anything from 2.5.0 onward is not.
Remediation
Update to version 2.5.0, 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.5.0 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