Ocean Extra <= 2.2.2 - Cross-Site Request Forgery to Arbitrary Plugin Activation
Strategic Overview
- Status
- Patched in 2.2.3
- Affected Plugin
- Ocean Extra
- Affected Version
<= 2.2.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-49164
At a glance
CVE-2023-49164 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Ocean Extra WordPress plugin, affecting versions <= 2.2.2. 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 2.2.3; sites on affected versions should update now. Disclosed November 2023, reported by Dave Jong.
Vulnerability Overview
The Ocean Extra plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.2. This is due to missing or incorrect nonce validation on the ajax_required_plugins_activate() function. This makes it possible for unauthenticated attackers to activate arbitrary plugins 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)
Ocean Extra <= 2.2.2 carries this weakness at ajax_required_plugins_activate(), 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 Ocean Extra the fix is 2.2.3: builds <= 2.2.2 are affected, anything from 2.2.3 onward is not.
Remediation
Update to version 2.2.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Ocean Extra: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ocean Extra 2.2.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Ocean Extra
- 7.5CVE-2019-16250: Ocean Extra <= 1.5.7 Options update and CSS injection
CVE-2019-16250 - 7.2CVE-2022-3374: Ocean Extra <= 2.0.4 PHP Object Injection
CVE-2022-3374 - 6.5CVE-2025-3472: Ocean Extra <= 2.4.6 Arbitrary Shortcode Execution
CVE-2025-3472 - 6.5CVE-2023-0749: Ocean Extra <= 2.1.2 Arbitrary Post Access
CVE-2023-0749 - 6.4CVE-2025-9499: Ocean Extra <= 2.4.9 Stored Cross-Site Scripting
CVE-2025-9499 - 6.4CVE-2025-3457: Ocean Extra <= 2.4.6 Stored Cross-Site Scripting
CVE-2025-3457 - 6.4CVE-2025-3458: Ocean Extra <= 2.4.6 Stored Cross-Site Scripting
CVE-2025-3458 - 6.4CVE-2024-37489: Ocean Extra <= 2.2.9 Stored Cross-Site Scripting
CVE-2024-37489
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C