Cowidgets Elementor AddonsWordPress extension · Codeless
CVE-2024-53786
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 Codeless Cowidgets – Elementor Addons cowidgets-elementor-addons allows Stored XSS.This issue affects Cowidgets – Elementor Addons: from n/a through <= 1.2.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 confidenceStored Cross-site Scripting (XSS) vulnerability in Codeless Cowidgets – Elementor Addons plugin (version <= 1.2.0) allows authenticated or unauthenticated attackers to inject malicious JavaScript scripts through unsanitized input that gets stored in the database and executed 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
Cowidgets Elementor AddonsWordPress extension
<= 1.2.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
- 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.
-
Confirm Cowidgets plugin is installedLog into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Cowidgets - Elementor Addons' or 'Codeless Cowidgets' in the list. Note the installed version displayed.Affected if The plugin is present and the version shows 1.2.0 or lower
-
Verify Elementor page builder is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm that Elementor Website Builder is installed and activated. This plugin is an Elementor addon, so the vulnerability only applies if Elementor is in use.Affected if Elementor is installed and active alongside Cowidgets
-
Inspect stored content in Elementor pages for unsanitized scriptsAccess your WordPress database (via phpMyAdmin or CLI) and query the wp_postmeta or wp_posts tables for script tags, iframe tags, or javascript: protocol handlers in content fields. Look for entries where meta_key contains 'elementor' or where post_content contains raw script tags.Affected if Any Elementor pages or widget content contains injected script tags or event handlers (onclick, onerror, etc.) that were not intentionally added by legitimate content editors
-
Review recent posts/pages for unexpected modificationsIn WordPress admin, check the Pages and Posts lists. Look for recent edits made by unknown users, or use the Revisions feature to compare current versions against previous ones for unexpected script injections.Affected if Recent posts or pages contain unauthorized JavaScript code that was not authored by legitimate administrators
You are affected if Cowidgets - Elementor Addons version 1.2.0 or lower is installed AND Elementor is active AND any stored XSS payloads exist in your database content.
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 Cowidgets – Elementor Addons to the latest version beyond 1.2.0. If no update is available, disable and remove the plugin until a patch is released.
Fix this in Cowidgets Elementor Addons
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53786 — 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-53786 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