dbcve.org
Ocean ExtraWordPress extension · Oceanwp

CVE-2024-37489

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to 2.3.0 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in OceanWP Ocean Extra allows Stored XSS.This issue affects Ocean Extra: from n/a through 2.2.9.

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 · high confidence

Stored Cross-Site Scripting (XSS) vulnerability in the OceanWP Ocean Extra WordPress plugin allows authenticated or unauthenticated attackers to inject malicious JavaScript code into web pages. The plugin fails to properly sanitize user input before rendering it in the page, causing the payload to execute in victims' browsers when they view affected content.

MitigationUpdate Ocean Extra plugin to the latest version (2.2.10 or later) which includes proper input sanitization. If patching is not immediately possible, disable or remove the plugin until update can be applied.

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.3.0

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
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ocean-extra/ directory exists on the server
    Affected if The Ocean Extra plugin is present in the WordPress installation
  2. Check installed version against affected range
    In WordPress admin, view the plugin details to see the version number, or read the main plugin file header in /wp-content/plugins/ocean-extra/ for the Version field
    Affected if The installed version is lower than 2.3.0 (for example, 2.2.9, 2.2.8, etc.)
  3. Identify input fields handled by the plugin
    Review which Ocean Extra features are in use: check plugin settings under OceanWP > Extra Options, and identify any user-supplied input forms or customizer fields provided by the plugin
    Affected if Any Ocean Extra features that accept and store user input are enabled and in use
  4. Inspect stored content for malicious payloads
    Search WordPress database (wp_posts, wp_postmeta tables) for suspicious script tags or event handlers in custom field values, meta boxes, or content areas associated with Ocean Extra functionality
    Affected if Stored XSS payloads containing <script> tags or javascript: handlers are found in plugin-related content

If Ocean Extra plugin is installed with a version below 2.3.0 and any plugin features that accept user input are in use, the environment is vulnerable to CVE-2024-37489

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.3.0 or later
Fixed in 2.3.0
Interim mitigation

Update Ocean Extra plugin to the latest version (2.2.10 or later) which includes proper input sanitization. If patching is not immediately possible, disable or remove the plugin until update can be applied.

Recommended fix High confidence

Ocean Extra 2.3.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Ocean Extra' in the plugin list
  4. Click 'Update Now' to update to the latest available version, or manually upload version 2.3.0 or later of the Ocean Extra plugin
  5. Verify the update was successful by checking the installed plugin version

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

Fix this in Ocean Extra Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37489 — 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-2024-37489 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