AccessPress Themes and Plugin <= Various Versions - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.4.3
- Affected Theme
- Arrival
- Affected Version
<= 1.4.2- 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 Arrival WordPress theme, affecting versions <= 1.4.2. 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 1.4.3; sites on affected versions should update now. Disclosed January 2022, reported by R3N0.
Vulnerability Overview
A WordPress plugin and several WordPress themes developed by AccessPress Themes are vulnerable to cross-site request forgery via the plugin_activation_callback and plugin_deactivate_callback functions, called via AJAX actions, that were missing capability checks and nonce validation. This makes it possible for unauthenticated attackers to deactivate and activate arbitrary plugins, granted they could trick a site administrator into performing an action such as clicking a link. This could be used to deactivate security plugins and exploit other potential vulnerabilities.
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 Arrival <= 1.4.2 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 Arrival the fix is 1.4.3: builds <= 1.4.2 are affected, anything from 1.4.3 onward is not.
Remediation
Update to version 1.4.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Arrival: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Arrival 1.4.3 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C