dbcve.org
Cowidgets Elementor AddonsWordPress extension · Codeless

CVE-2024-8960

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-09
Fix available
A fix is available. Upgrade to after 1.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The Cowidgets – Elementor Addons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.2.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

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 confidence

The Cowidgets – Elementor Addons WordPress plugin versions up to 1.2.0 fail to properly sanitize SVG file uploads, allowing authenticated users with Author-level permissions or higher to embed malicious JavaScript within SVG files. When users access these uploaded files, the embedded scripts execute in their browsers, enabling stored XSS attacks.

MitigationUpdate the Cowidgets plugin to version 1.2.1 or later which contains the fix. Until updated, restrict upload capabilities for lower-privileged users and consider disabling SVG uploads at the server level.

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
Affected:<= 1.2.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Cowidgets plugin version
    Go to WordPress Admin > Plugins > Installed Plugins and locate 'Codeless Cowidgets Elementor Addons'. Read the version number displayed under the plugin name.
    Affected if The version listed is 1.2.0 or lower.
  2. Verify SVG upload capability exists
    Navigate to Media Library (Media > Library). Click 'Add New' and check if SVG file type is accepted in the upload area, or attempt to upload a test SVG file with an Administrator account.
    Affected if SVG files can be uploaded through the WordPress media uploader.
  3. Identify users with Author or higher role
    Go to Users > All Users in WordPress admin. Review the 'Role' column for each user. Count users with role 'Author', 'Editor', or 'Administrator'.
    Affected if At least one user exists with Author, Editor, or Administrator role.
  4. Inspect recent SVG uploads in media library
    Go to Media > Library. Use the filter or search to locate files with .svg extension. Check the 'Uploaded to' column to see which user account uploaded them. Review file names for suspicious patterns (random strings, encoded characters).
    Affected if Any SVG files were uploaded by users with Author-level or higher permissions.
  5. Review uploaded SVG file contents
    Download a sample SVG from the media library. Open the file in a text editor and examine the contents for <script> tags, javascript: protocol handlers, onload/onerror attributes, or other embedded JavaScript.
    Affected if The SVG file contains any executable JavaScript code or event handlers.

A user is affected if the Cowidgets plugin version is 1.2.0 or lower AND Author-level or higher users can upload SVG files to the media library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.0
Interim mitigation

Update the Cowidgets plugin to version 1.2.1 or later which contains the fix. Until updated, restrict upload capabilities for lower-privileged users and consider disabling SVG uploads at the server level.

Recommended fix Moderate confidence

1.2.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Dashboard > Plugins > Installed Plugins
  3. Locate 'Cowidgets – Elementor Addons' in the plugin list
  4. Click 'Update Now' to install the latest available version
  5. Verify the update completes successfully and the plugin is now at version 1.2.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cowidgets Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8960 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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