Otter BlocksWordPress extension · Themeisle
CVE-2024-1684
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 · uneditedThe Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the contact form file field CSS metabox in all versions up to, and including, 2.6.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe Otter Blocks WordPress plugin versions up to 2.6.3 contain a stored XSS vulnerability in the contact form file field CSS metabox. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through insufficiently sanitized input, which executes when other users access affected pages.
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
Otter BlocksWordPress extension
< 2.6.4CVSS 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 Otter Blocks plugin is installedGo to WordPress admin > Plugins > Installed Plugins and look for 'Otter Blocks' by Themeisle. Note the installed version number.Affected if Plugin version is shown as anything below 2.6.4 (or version is unknown/cannot be determined and plugin is active)
-
Verify contact form module is activeCheck if the Otter Blocks plugin includes the Contact Form block. This can be done by creating a new post/page and searching for 'Contact Form' in the block inserter, or by checking the plugin's block availability.Affected if The Contact Form block is available and appears to be from Otter Blocks plugin
-
Identify pages/posts using the Contact Form blockSearch the WordPress database for posts containing the Otter Contact Form block. In phpMyAdmin or via WP-CLI: SELECT * FROM wp_posts WHERE post_content LIKE '%otter-contact-form%' (adjust prefix as needed).Affected if Any posts or pages contain the Contact Form block from Otter Blocks
-
Inspect Contact Form block settings for injected scriptsEdit a page/post containing the Contact Form block, select the block, and check the block settings panel (usually in the right sidebar) for any Custom CSS or field configuration containing suspicious script tags, event handlers, or unusual JavaScript references.Affected if The block settings contain unexpected JavaScript code, script tags, or onclick/onload attributes in CSS fields
-
Review page source for XSS executionView a published page with the Contact Form block in a browser, right-click > View Page Source, and search for script tags or unusual inline event handlers (onclick, onload, onerror) that were not intentionally added.Affected if Unexpected script tags or JavaScript event handlers are present in the rendered HTML
If Otter Blocks version is below 2.6.4 AND the Contact Form block is in use, the environment is potentially affected by this stored XSS vulnerability.
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.6.4
Update to plugin version 2.6.4 or later which addresses the input sanitization and output escaping issues. Review and remove any existing malicious scripts from affected pages.
2.6.4
- Backup your WordPress site before making any changes
- Navigate to WordPress Dashboard > Plugins > Installed Plugins
- Locate 'Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE' in the plugin list
- Click 'Update now' if an update is available, or manually update to version 2.6.4
- After updating, verify the plugin version shows 2.6.4 in the plugins list
- Test that the contact form functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Otter Blocks
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1684 — 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-2024-1684 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