Strategic Overview
- Status
- Patched in 1.46
- Affected Plugin
- We’re Open!
- Affected Version
<= 1.45- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-25067
At a glance
CVE-2023-25067 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the We’re Open! WordPress plugin, affecting versions <= 1.45. 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 1.46; sites on affected versions should update now. Disclosed February 2023, reported by István Márton.
Vulnerability Overview
The We’re Open! plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.45. This is due to missing or incorrect nonce validation on the admin_ajax function called via the we_are_open_admin_ajax AJAX action. This function triggers multiple cases (update, delete, google_business_credentials, google_data, google_business, separators, logo-delete, logo_delete, logo-remove, logo_remove, logo, structured-data, structured_data, google_data_preview, custom-styles, custom_styles clear, cache, clear-cache, clear_cache, and reset). This makes it possible for unauthenticated attackers to perform unauthorized administrative actions 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 We’re Open! <= 1.45 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 We’re Open! the fix is 1.46: builds <= 1.45 are affected, anything from 1.46 onward is not.
Remediation
Update to version 1.46, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to We’re Open!: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: We’re Open! 1.46 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