Ocean Extra <= 2.1.2 - Authenticated (Subscriber+) Arbitrary Post Access
Strategic Overview
- Status
- Patched in 2.1.3
- Affected Plugin
- Ocean Extra
- Affected Version
<= 2.1.2- CVSS
- 6.5Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-0749
At a glance
CVE-2023-0749 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Ocean Extra WordPress plugin, affecting versions <= 2.1.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.3; sites on affected versions should update now. Disclosed February 2023, reported by Erwan LR.
Vulnerability Overview
The Ocean Extra for WordPress is vulnerable to disclosure of potentially sensitive data in versions up to, and including, 2.1.2. This is due to to the [oceanwp_library] shortcode not properly validating a post's status prior to returning the post's content. This makes it possible for authenticated attackers with subscriber-level permissions and above to retrieve arbitrary post content, even when it is in a pre-published or private status.
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 interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Ocean Extra <= 2.1.2 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Ocean Extra the fix is 2.1.3: builds <= 2.1.2 are affected, anything from 2.1.3 onward is not.
Remediation
Update to version 2.1.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Ocean Extra 2.1.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
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.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 - 6.4CVE-2024-5531: Ocean Extra <= 2.2.8 Stored Cross-Site Scripting
CVE-2024-5531
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C