Ocean ExtraWordPress extension · Oceanwp
CVE-2023-23891
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in OceanWP Ocean Extra plugin <= 2.1.1 versions. Needs the OceanWP theme installed and activated.
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 confidenceAuthenticated contributor+ users can inject malicious JavaScript via the OceanWP Ocean Extra plugin (versions <= 2.1.1) due to insufficient input sanitization. The stored XSS payload executes when users view content rendered by the OceanWP theme.
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
< 2.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm OceanWP Ocean Extra plugin is installedNavigate to WordPress admin dashboard > Plugins and locate OceanWP Ocean Extra in the installed plugins listAffected if OceanWP Ocean Extra appears in the plugins list and is activated
-
Identify the installed version of OceanWP Ocean ExtraIn the Plugins list, click on the plugin to view details or check the version number displayed in the plugin rowAffected if The displayed version is 2.1.1 or lower (any version prior to 2.1.2)
-
Check for contributor-level or higher user accountsNavigate to WordPress admin > Users and review the user list to identify any accounts with Contributor, Author, Editor, or Administrator rolesAffected if At least one user account with Contributor or higher role exists on the site
-
Verify OceanWP theme is activeNavigate to WordPress admin > Appearance > Themes and confirm whether the OceanWP theme is currently activatedAffected if OceanWP theme is the active theme on the site
The environment is affected if OceanWP Ocean Extra plugin is installed at version 2.1.1 or below, contributor-plus user accounts exist, and the OceanWP theme is active, allowing stored XSS to execute when content is viewed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.1.2
Update OceanWP Ocean Extra plugin to the latest version or remove/disable the plugin if the OceanWP theme is not actively in use.
2.1.2
- Navigate to your WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the Ocean Extra plugin
- Update the plugin to version 2.1.2 or later
- Verify the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ocean Extra
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23891 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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