dbcve.org
Ocean ExtraWordPress extension · Oceanwp

CVE-2023-24399

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-30
Fix available
A fix is available. Upgrade to 2.1.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in OceanWP Ocean Extra plugin <= 2.1.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authenticated users with contributor-level or higher privileges can inject malicious JavaScript code through the Ocean Extra plugin's input fields. This stored XSS payload persists in the database and executes when other users (including administrators) view the affected content in the WordPress admin dashboard or frontend.

MitigationUpdate OceanWP Ocean Extra plugin to a version higher than 2.1.2. Additionally, implement proper input sanitization and output encoding as defense-in-depth while awaiting the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ocean ExtraWordPress extension
Affected:< 2.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Ocean Extra plugin is installed
    Navigate to WordPress admin dashboard > Plugins. Look for 'Ocean Extra' in the installed plugins list.
    Affected if Ocean Extra plugin is present in the plugins list
  2. Check installed Ocean Extra version
    In Plugins page, locate Ocean Extra and note the version number displayed beneath the plugin name. Alternatively, access via FTP/SFTP and read the main plugin file (usually ocean-extra/ocean-extra.php) to find the 'Version' header in the plugin comments.
    Affected if Version is listed as lower than 2.1.3 or the version header is missing or unreadable
  3. Identify users with contributor-level or higher access
    In WordPress admin, go to Users > All Users. Review the 'Role' column for any users assigned roles of Contributor, Author, Editor, or Administrator.
    Affected if At least one user exists with Contributor, Author, Editor, or Administrator role
  4. Inspect database for injected script content
    Access phpMyAdmin or use WP-CLI: `wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%onload=%' LIMIT 50;"` (adjust table prefix if different from 'wp_'). Also check wp_postmeta and wp_options for suspicious JavaScript patterns.
    Affected if Database records contain unrecognized script tags, event handlers (onerror, onload, onclick), or encoded JavaScript that was not intentionally added by administrators

Environment is affected if Ocean Extra plugin version is below 2.1.3 AND at least one user with contributor-level or higher privileges exists AND suspicious script content is found in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.3 or later
Fixed in 2.1.3
Interim mitigation

Update OceanWP Ocean Extra plugin to a version higher than 2.1.2. Additionally, implement proper input sanitization and output encoding as defense-in-depth while awaiting the patch.

Recommended fix High confidence

Ocean Extra version 2.1.3 or higher

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate Ocean Extra plugin in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 2.1.3 or higher from the WordPress plugin repository
  5. Verify the plugin updated successfully by checking the version number
  6. Consider testing the update in a staging environment first if available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ocean Extra Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24399 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24399 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data