CVE-2024-24930
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in OTWthemes.Com Buttons Shortcode and Widget allows Stored XSS.This issue affects Buttons Shortcode and Widget: from n/a through 1.16.
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 confidenceStored XSS vulnerability in OTWthemes.Com Buttons Shortcode and Widget plugin allows attackers to inject malicious JavaScript through unsanitized input fields in button shortcodes or widgets, which then executes when other users view the affected pages.
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<= 1.16CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate plugin installation directoryAccess your WordPress site via FTP or file manager and navigate to wp-content/plugins/ directory. Look for a folder named 'otwthemes-buttons-shortcode-and-widget' or similar variant containing 'otwthemes' and 'buttons'.Affected if The plugin folder exists in wp-content/plugins/
-
Identify installed plugin versionOpen the main plugin file (usually named like otwthemes-buttons.php or similar in the plugin folder) and locate the version header in the plugin comment block at the top. Alternatively, check the readme.txt file for the 'Stable tag' or 'Version' entry.Affected if The reported version number is 1.16 or lower (e.g., 1.16, 1.15, 1.14, etc.)
-
Confirm plugin is activeLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Verify that the Otwthemes Buttons Shortcode And Widget plugin shows as 'Active'.Affected if The plugin appears in the active plugins list
-
Identify shortcode or widget usageSearch your WordPress database or inspect page/post content for instances of the button shortcode (typically [otw_button] or similar variations) in posts, pages, or widget areas. Use phpMyAdmin to query wp_posts table for post_content containing 'otw_button' or 'otwthemes' strings.Affected if Active use of the plugin's shortcode or widget with user-supplied text fields (such as button text, URL, or styling attributes) is present in your content
Your environment is affected if the Otwthemes Buttons Shortcode And Widget plugin is installed with version 1.16 or lower and is actively used via shortcodes or widgets containing user-supplied input on your site.
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 the latest patched version. If no patch is available, disable the plugin. Implement input validation using WordPress sanitization functions (esc_html, esc_attr, wp_kses) on all user-supplied values before output.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24930 — 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-24930 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