WP Meteor Page Speed Optimization Topping <= 3.1.4 - Cross-Site Request Forgery via processAjaxNoticeDismiss
Strategic Overview
- Status
- Patched in 3.1.5
- Affected Plugin
- WP Meteor Website Speed Optimization Addon
- Affected Version
<= 3.1.4- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-26543
At a glance
CVE-2023-26543 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Meteor Website Speed Optimization Addon WordPress plugin, affecting versions <= 3.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.5; sites on affected versions should update now. Disclosed February 2023, reported by Muhammad Daffa.
Vulnerability Overview
The WP Meteor Page Speed Optimization Topping plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.4. This is due to missing or incorrect nonce validation on the processAjaxNoticeDismiss function. This makes it possible for unauthenticated attackers to dismiss admin notices 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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WP Meteor Website Speed Optimization Addon <= 3.1.4 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 WP Meteor Website Speed Optimization Addon the fix is 3.1.5: builds <= 3.1.4 are affected, anything from 3.1.5 onward is not.
Remediation
Update to version 3.1.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Meteor Website Speed Optimization Addon: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Meteor Website Speed Optimization Addon 3.1.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP Meteor Website Speed Optimization Addon
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C