CVE-2023-29386
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 Julien Crego Manager for Icomoon.This issue affects Manager for Icomoon: from n/a through 2.0.
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 confidenceUnrestricted file upload vulnerability in Manager for Icomoon plugin allowing unauthenticated attackers to upload dangerous file types (e.g., PHP scripts) that can be executed on the server, potentially achieving remote code execution. The CVSS 9.1 indicates network exploitability with no authentication required and complete impact on confidentiality, integrity, and availability.
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.
-
Identify if Manager for Icomoon plugin is installedCheck your website's plugin directory or admin panel for 'Manager for Icomoon' or 'icomoon' plugin entries. If using a file system, search for directories or files containing 'icomoon' in the plugins folder.Affected if The plugin is present on the system
-
Locate the file upload componentSearch for upload-handling scripts within the plugin directory, typically in paths like /manager-icomoon/, /icomoon-manager/, or similar. Look for PHP files that handle file uploads (functions like move_uploaded_file, $_FILES).Affected if Upload functionality exists within the plugin
-
Test if dangerous file extensions are acceptedAttempt to upload a test file with a .php extension (or other script extensions like .phtml, .php5) to the plugin's upload endpoint using a tool like curl or Burp Suite. Check if the file is accepted without validation errors.Affected if The upload accepts and stores .php or other executable file extensions
-
Verify upload directory is web-accessibleIf uploads are successful, check if the upload directory is accessible via HTTP/HTTPS. Try to access the uploaded file directly in a browser.Affected if Uploaded files are stored in a web-accessible directory and can be executed via HTTP request
-
Confirm script execution is not blockedIf you can access the uploaded file URL, verify whether the server executes the PHP code or serves it as plain text. A vulnerable system will execute the script.Affected if The server executes uploaded PHP files rather than serving them as plain text
A system is affected if the Manager for Icomoon plugin is installed and its upload functionality allows unauthenticated upload of executable file types that can be accessed and executed via the web server.
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 including magic byte verification, store uploads outside the web root, rename files upon upload, and ensure uploaded files cannot be executed (e.g., disable script execution in upload directories).
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29386 — 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-2023-29386 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