CVE-2024-47649
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 THATplugin Iconize iconize.This issue affects Iconize: from n/a through <= 1.2.4.
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 confidenceA critical file upload vulnerability in the Iconize WordPress plugin (versions up to 1.2.4) allows unauthenticated attackers to upload dangerous file types without restriction. The CVSS 9.1 score indicates this likely enables remote code execution by uploading executable files (e.g., PHP scripts) to the server's web root.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Verify Iconize plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Iconize' in the list of active plugins.Affected if The Iconize plugin appears in the installed plugins list, regardless of activation status, since unauthenticated attackers can exploit the vulnerability.
-
Check installed Iconize plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Click on the Iconize plugin to view its details, or check the plugin files in /wp-content/plugins/ for a version indicator in the main PHP file.Affected if The installed version is 1.2.4 or any earlier version, as versions up to and including 1.2.4 are affected.
-
Inspect plugin file upload codeExamine the Iconize plugin PHP files, specifically looking for any upload handling functions or endpoints. Search for terms like 'upload', 'file', 'POST', and 'move_uploaded_file' within the plugin directory.Affected if The plugin contains file upload functionality or handler code that lacks proper file type validation or authentication checks.
-
Review uploads directory for suspicious filesNavigate to /wp-content/uploads/ (or the configured upload directory) and list all files. Look for unexpected file types such as .php, .phtml, .phar, or other executable extensions.Affected if Any PHP files or other executable scripts exist in the uploads directory that were not intentionally placed there by administrators.
-
Check web server access logs for Iconize upload requestsReview web server access logs (Apache/nginx) for POST requests to Iconize plugin endpoints, particularly those targeting upload-related paths. Look for unusual file extensions in the request.Affected if Log entries show unauthenticated POST requests to Iconize-related upload endpoints with suspicious file extensions like .php.
You are affected if the Iconize plugin is installed with version 1.2.4 or earlier, or if any unexplained executable files appear in your uploads 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 dataUpdate Iconize plugin to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Additionally, implement web application firewall rules to block malicious file uploads and restrict file upload directories from execution permissions.
- 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-47649 — 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-47649 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