dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-24370

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 ('Cross-site Scripting') vulnerability in Theme-one The Grid the-grid allows Stored XSS.This issue affects The Grid: from n/a through < 2.8.0.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in the Theme-one The Grid WordPress plugin (versions before 2.8.0). The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing malicious JavaScript to be stored and executed in the browsers of users who view affected content.

MitigationUpdate The Grid plugin to version 2.8.0 or later which contains the security patch. Until then, restrict editor-level access to trusted users only and consider additional web application firewall rules.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Confirm The Grid plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the plugin directory (wp-content/plugins/the-grid) for the presence of The Grid plugin files
    Affected if The Grid plugin files exist in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, view plugin details for The Grid to see the version number, or read the main plugin file header (e.g., the-grid.php) to find the Version field
    Affected if The version number is below 2.8.0 (e.g., 2.7.x, 2.6.x, etc.)
  3. Identify user input sources in grid content
    Review any grid items, custom post types, or content created using The Grid plugin. Examine where user-supplied text, URLs, or metadata are saved and displayed in grid layouts
    Affected if User-generated content (titles, descriptions, meta fields, custom URLs) is stored and rendered in grid displays without additional sanitization
  4. Verify editor-level access is unrestricted
    Check WordPress user roles and capabilities. Navigate to Users > All Users and review which users have Editor or Contributor roles who can create The Grid content
    Affected if Untrusted or unverified users have Editor-level access and can create or modify The Grid content items

You are affected if The Grid plugin is installed with a version below 2.8.0 AND untrusted users can add or modify grid content that gets displayed on the 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 The Grid plugin to version 2.8.0 or later which contains the security patch. Until then, restrict editor-level access to trusted users only and consider additional web application firewall rules.

Recommended fix Moderate confidence

2.8.0

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate 'The Grid' (the-grid) in the plugin list.
  4. 4. Check if the current installed version is below 2.8.0.
  5. 5. If vulnerable, update the plugin to version 2.8.0 or later via the WordPress plugin update mechanism, or manually upload version 2.8.0 from the WordPress plugin repository.
  6. 6. After updating, verify the plugin version shows 2.8.0 or higher.
  7. 7. Clear any site caches if a caching plugin is in use.
  8. 8. Test the grid functionality to ensure the update did not break existing features.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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