dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-8760

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The Stackable – Page Builder Gutenberg Blocks plugin for WordPress is vulnerable to CSS Injection in all versions up to, and including, 3.13.6. This makes it possible for unauthenticated attackers to embed untrusted style information into comments resulting in a possibility of data exfiltration such as admin nonces with limited impact. These nonces could be used to perform CSRF attacks within a limited time window. The presence of other plugins may make additional nonces available, which may pose a risk in plugins that don't perform capability checks to protect AJAX actions or other actions reachable by lower-privileged users.

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

The Stackable WordPress plugin up to version 3.13.6 allows unauthenticated attackers to inject malicious CSS into comments. Attackers can craft CSS that causes the victim's browser to exfiltrate admin nonces by embedding nonce values in style requests (e.g., background-image URLs), which can then be used for CSRF attacks against admin actions within a limited time window.

MitigationUpdate to plugin version 3.13.7 or later which contains the fix. If no update is available, consider removing the plugin. Additionally, audit other installed plugins for AJAX actions lacking capability checks that could be exploited with stolen nonces.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Stackable plugin is installed
    Go to WordPress admin > Plugins and look for 'Stackable' in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' LIKE '%stackable%'
    Affected if Stackable plugin is present in the WordPress installation
  2. Check installed Stackable version
    In WordPress admin > Plugins, find Stackable and view the version number displayed below the plugin name, or query: SELECT option_value FROM wp_options WHERE option_name LIKE '%stackable%version%'
    Affected if The displayed version is 3.13.6 or lower
  3. Confirm comment functionality is enabled
    In WordPress admin > Settings > Discussion, verify that 'Allow people to submit comments on new posts' is checked, or query: SELECT option_value FROM wp_options WHERE option_name = 'default_comment_status'
    Affected if Comments are enabled on the site (default_comment_status = 'open')
  4. Check if plugin is actively running
    Query active_plugins in wp_options: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check if stackable is in the serialized array
    Affected if Stackable is in the active plugins list and the version is 3.13.6 or below

The environment is affected if the Stackable plugin version 3.13.6 or lower is installed, active, and comments are enabled on the WordPress site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to plugin version 3.13.7 or later which contains the fix. If no update is available, consider removing the plugin. Additionally, audit other installed plugins for AJAX actions lacking capability checks that could be exploited with stolen nonces.

Recommended fix Moderate confidence

3.13.7 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Stackable – Page Builder Gutenberg Blocks' plugin
  4. If the plugin shows version 3.13.6 or lower, click 'Update Now' to upgrade to the latest version
  5. Alternatively, navigate to Dashboard > Updates and apply available updates
  6. After updating, verify the plugin version is 3.13.7 or higher under Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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