CVE-2024-49676
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Michael Bourne Custom Icons for Elementor custom-icons-for-elementor allows Upload a Web Shell to a Web Server.This issue affects Custom Icons for Elementor: from n/a through <= 0.3.3.
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 confidenceThe Custom Icons for Elementor plugin lacks proper file type validation during icon uploads, allowing unauthenticated attackers to upload executable files (web shells) to the web server. This unrestricted file upload vulnerability can lead to remote code execution.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
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.
-
Verify if the Custom Icons for Elementor plugin is installedCheck your WordPress plugins directory or dashboard for 'Custom Icons for Elementor'Affected if The plugin is present in the installation
-
Identify the installed plugin versionAccess the plugin files (typically wp-content/plugins/custom-icons-for-elementor/) and check the main PHP file for the version constant, or view it in the WordPress plugin admin panelAffected if The installed version has not been patched and falls within the vulnerable range
-
Confirm the upload endpoint is accessibleCheck if the WordPress site allows unauthenticated access to the icon upload functionality - inspect the plugin's ajax handlers or upload forms to verify capability requirementsAffected if The upload functionality does not enforce authentication or authorization checks
-
Inspect the upload directory configurationLocate the directory where icon uploads are stored (check plugin code for upload path) and verify file permissions - files should not be executable or stored in a web-accessible directory with script execution enabledAffected if Uploaded files can be executed as scripts (e.g., .php files in a publicly accessible directory)
-
Review file type validation logicExamine the plugin source code for functions handling file uploads - look for proper file type validation, mime type checking, or extension allowlisting before processing uploadsAffected if There is no server-side validation or the validation relies solely on client-side checks or file extension renaming
You are affected if the plugin is installed without patches, the upload endpoint accepts unauthenticated requests, and uploaded files can be executed as scripts from the web directory.
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 dataImplement strict allowlist-based file type validation, restrict upload directory permissions, sanitize uploaded SVG content, and ensure uploaded files cannot be executed as scripts.
- 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-49676 — 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-49676 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