CVE-2024-10910
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 The Grid Plus – Unlimited grid layout plugin for WordPress is vulnerable to arbitrary shortcode execution via grid_plus_load_by_category AJAX action in all versions up to, and including, 1.3.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
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 Grid Plus WordPress plugin versions up to 1.3.5 contain an insecure AJAX endpoint (grid_plus_load_by_category) that accepts user input and passes it directly to WordPress's do_shortcode() function without validation or sanitization. This allows unauthenticated attackers to execute any registered shortcode on the site, potentially leading to data exfiltration, privilege escalation, or remote code execution depending on what shortcodes are available.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Grid Plus plugin is installedNavigate to WordPress admin dashboard > Plugins and confirm Grid Plus is listed as an active or installed pluginAffected if Grid Plus plugin is present on the site
-
Check installed version numberIn the Plugins list, look for the version number displayed under the Grid Plus plugin entry, or check the plugin header in its main PHP fileAffected if Version is 1.3.5 or lower (any version up to and including 1.3.5)
-
Confirm the vulnerable AJAX endpoint existsMake a POST request to wp-admin/admin-ajax.php with action=grid_plus_load_by_category and a test shortcode in the parameters (e.g., category parameter set to a shortcode like [example])Affected if The endpoint responds and processes shortcode input without requiring authentication or validation
-
Identify registered shortcodes that could be exploitableSearch plugin files for add_shortcode() calls, or use a WordPress function to list registered shortcodes via theme functions.php or a debugging pluginAffected if Any registered shortcode can be invoked through the vulnerable endpoint, especially those that access sensitive data or execute code
The site is affected if Grid Plus plugin version is 1.3.5 or lower AND the AJAX endpoint grid_plus_load_by_category is accessible and processes shortcode input without validation.
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.
From vendor dataUpdate to version 1.3.6 or later which patches this vulnerability; if no update is available, disable the plugin or add server-side filtering to block the vulnerable AJAX endpoint until a patch is released.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10910 — 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-10910 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