CVE-2024-51638
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Sanjeev Mohindra Awesome Shortcodes For Genesis awesome-shortcodes-for-genesis allows Stored XSS.This issue affects Awesome Shortcodes For Genesis: from n/a through 1.1.8.
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 confidenceA CSRF vulnerability in the Awesome Shortcodes For Genesis WordPress plugin enables attackers to inject malicious scripts (Stored XSS) by tricking authenticated administrators into submitting crafted requests. The lack of proper nonce validation on admin actions allows cross-site request forgery, and insufficient input sanitization on stored data enables persistent script injection.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedLocate the plugin directory 'awesome-shortcodes-for-genesis' in wp-content/plugins/ or view it in WordPress admin under Plugins > Installed PluginsAffected if The plugin appears in the installed plugins list
-
Check the installed versionView the plugin version in WordPress admin (Plugins > Installed Plugins > Awesome Shortcodes For Genesis) or read the 'Version:' field in the plugin's main PHP file headerAffected if The version number is lower than the patched release and cannot be determined to be secure
-
Confirm the plugin is activeCheck if the plugin shows as 'Active' in WordPress admin under Plugins > Installed PluginsAffected if The plugin is currently activated on the site
-
Identify admin-facing features that accept user inputReview the plugin's admin menu options and settings pages for any fields that accept and store user input (shortcode configuration, content fields, settings forms)Affected if The plugin has admin settings pages where data is saved to the database
-
Verify nonce implementation on admin actionsExamine the plugin's PHP source code for proper nonce verification (wp_nonce_field, wp_verify_nonce, check_admin_referer) on form submissions and AJAX handlers in admin areasAffected if Admin actions lack proper nonce validation and the plugin version is unpatched
You are affected if you have an unpatched version of Awesome Shortcodes For Genesis plugin installed and active with admin-accessible input fields that lack proper nonce validation and input sanitization.
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 the latest version of Awesome Shortcodes For Genesis to receive the security patch. Review and implement proper nonce verification for all admin-side actions and sanitize all user inputs before storage and output.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51638 — 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-51638 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