dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-24707

CRITICAL · 9.9 CVSS v3.1 Published 2024-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Improper Control of Generation of Code ('Code Injection') vulnerability in Cwicly Builder, SL. Cwicly allows Code Injection.This issue affects Cwicly: from n/a through 1.4.0.2.

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 confidence

Cwicly Builder plugin for WordPress contains a code injection vulnerability that allows attackers to inject malicious code through the plugin's code injection functionality. The improper control of code generation combined with a critical CVSS score indicates this could allow remote attackers to execute arbitrary code on the WordPress installation.

MitigationUpgrade to a patched version of Cwicly Builder beyond 1.4.0.2 that properly validates and sanitizes code injection inputs, or disable the code injection feature until a fix is available.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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. Confirm Cwicly Builder is installed
    Navigate to WordPress admin > Plugins and look for 'Cwicly Builder' in the installed plugins list, or check the wp-content/plugins directory for the cwicly folder
    Affected if Cwicly Builder plugin is present on the WordPress installation
  2. Identify the installed version
    In WordPress admin > Plugins > Installed Plugins, find Cwicly Builder and note the version number displayed below the plugin name. Alternatively, check the 'Version' field in the plugin's main PHP file header located at wp-content/plugins/cwicly/core.php
    Affected if The displayed version is 1.4.0.2 or lower, indicating the plugin is in the vulnerable version range
  3. Verify the code injection feature is enabled
    Go to Cwicly Builder settings in the WordPress admin panel. Look for a Code Injection or similar settings section. Check if any code injection fields contain content or if the feature toggle is turned on
    Affected if The code injection feature contains custom code entries or is enabled, meaning the vulnerable functionality is active on the site
  4. Inspect code injection configuration for untrusted content
    Navigate to the code injection settings area and review any PHP, JavaScript, or other code that has been added. Look for suspicious or unfamiliar code patterns that may indicate compromise
    Affected if The code injection settings contain code that was not added by a trusted administrator, suggesting potential exploitation

A user is affected if Cwicly Builder version 1.4.0.2 or lower is installed AND the code injection feature is enabled or contains configuration entries on their WordPress site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Cwicly Builder beyond 1.4.0.2 that properly validates and sanitizes code injection inputs, or disable the code injection feature until a fix is available.

Recommended fix Moderate confidence

Any version after 1.4.0.2 (e.g., 1.4.0.3 or later if available)

  1. 1. Log in to the WordPress admin dashboard where Cwicly Builder is installed.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate Cwicly Builder in the plugin list.
  4. 4. Check if an update is available for Cwicly Builder.
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. Alternatively, download the latest version of Cwicly Builder from the official WordPress repository or from the vendor's website.
  7. 7. Deactivate the current Cwicly Builder plugin, then delete it, and install the fresh updated version.
  8. 8. After updating, verify the plugin is active and test that the website functionality remains intact.
Caveat Review changelog for potential breaking changes between 1.4.0.2 and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24707 — 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-24707 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