CVE-2024-33644
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 Control of Generation of Code ('Code Injection') vulnerability in WPCustomify Customify Site Library allows Code Injection.This issue affects Customify Site Library: from n/a through 0.0.9.
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 confidenceThe WPCustomify Customify Site Library plugin for WordPress versions through 0.0.9 contains a code injection vulnerability allowing attackers to inject and execute arbitrary code. This improper control of code generation enables complete site compromise.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Customify Site Library pluginCheck the wp-content/plugins/ directory for a folder named 'customify-site-library' or similar. Also check the WordPress admin Plugins page for the presence of this plugin.Affected if The plugin folder or listing is found in the WordPress plugins directory
-
Identify the installed versionOpen the main plugin PHP file (usually customify-site-library.php) and look for the 'Version' header in the plugin comment block, or check the readme.txt file for the version field.Affected if The version number is 0.0.9 or lower (including any 0.0.x version)
-
Confirm plugin is activeCheck the WordPress database wp_options table for the option 'active_plugins', or use the admin dashboard to verify the plugin status.Affected if The plugin appears in the list of active plugins
-
Identify code generation functionalitySearch plugin files for functions related to code generation, eval(), file_put_contents(), or other code execution methods. Look for any template import, code snippet, or custom CSS/JS generation features.Affected if The plugin contains code generation or dynamic code execution features that are accessible
-
Check for unauthenticated access to vulnerable endpointsReview the plugin's AJAX handlers or public-facing PHP files to determine if the code generation functionality can be accessed without authentication.Affected if The code generation feature can be accessed by unauthenticated users or low-privilege accounts
If the Customify Site Library plugin is installed, active, and running version 0.0.9 or lower, the environment is affected by this code 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 Customify Site Library to the latest patched version. If no patch is available, disable or remove the plugin until a fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33644 — 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-33644 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