Enable Shortcodes Inside Widgets\,comments And ExpertsWordPress extension · Aftabhusain
CVE-2024-9846
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 Enable Shortcodes inside Widgets,Comments and Experts plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.0.0. 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 · moderate confidenceThe Enable Shortcodes inside Widgets, Comments and Experts WordPress plugin fails to properly validate user input before passing it to WordPress's do_shortcode function. This allows unauthenticated attackers to inject and execute arbitrary shortcodes on the affected site, potentially leading to information disclosure, content manipulation, or further exploitation depending on what shortcodes are registered.
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
Enable Shortcodes Inside Widgets\,comments And ExpertsWordPress extension
<= 1.0.0CVSS 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.
-
Check if the plugin is installed and activeNavigate to WordPress Admin > Plugins and look for 'Enable Shortcodes Inside Widgets, Comments and Experts' by Aftabhusain. Alternatively, check the /wp-content/plugins/ directory for a folder related to this plugin.Affected if The plugin is installed and active on the WordPress site
-
Verify the installed versionIn WordPress Admin > Plugins page, locate the plugin and view its version number under the plugin name. Compare against the affected range: <= 1.0.0Affected if The installed version is 1.0.0 or any version below 1.0.0
-
Confirm the vulnerable functionality is in useThe vulnerability allows unauthenticated shortcode injection. Check if the plugin processes user input in widgets, comments, or other user-submitted content areas. Submit a test shortcode (e.g., a simple registered shortcode) in a comment form or widget to see if it executes.Affected if User-supplied content in comments, widgets, or similar areas is processed through do_shortcode without validation
If the plugin is active and the version is 1.0.0 or lower, the site is affected by this unauthenticated shortcode injection 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.
From vendor dataUpdate the plugin to a patched version once released. Until then, consider disabling the plugin if not essential, or deploy a WAF rule to block requests containing shortcode-related parameters.
Fix this in Enable Shortcodes Inside Widgets\,comments And Experts
Scoped from the published advisory
- 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-9846 — 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-9846 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