Instawp ConnectWordPress extension · Instawp
CVE-2024-37228
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 InstaWP InstaWP Connect instawp-connect.This issue affects InstaWP Connect: from n/a through <= 0.1.0.38.
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 InstaWP Connect plugin allows attackers to upload dangerous file types (likely executable files like PHP) without proper validation, leading to potential remote code execution and complete site compromise. The vulnerability affects all versions through 0.1.0.38.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Instawp ConnectWordPress extension
< 0.1.0.39CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 InstaWP Connect plugin is installedCheck your WordPress plugins directory for the instawp-connect folder, or use WP-CLI: wp plugin list --name='instawp-connect'Affected if The plugin is present in the environment
-
Determine installed plugin versionRead the main plugin file header (usually instawp-connect.php) to find the Version: X.X.X.X field, or use: wp plugin get instawp-connect --field=versionAffected if Version is 0.1.0.38 or lower (anything below 0.1.0.39)
-
Check for accessible upload endpointsReview web server access logs for POST requests to common upload paths such as /wp-content/uploads/instawp/, /wp-admin/admin-ajax.php?action=instawp_upload, or any endpoint containing 'upload' in the URL patternAffected if Upload endpoints are publicly accessible without additional authentication beyond basic WordPress auth
-
Inspect upload directories for suspicious filesExamine the wp-content/uploads/instawp/ directory (and any custom upload paths) for file extensions such as .php, .phtml, .phar, .exe, or .js that should not be present in upload foldersAffected if Executable or script files (.php, .phtml, etc.) exist in upload directories
-
Review recent file modifications in upload foldersCheck file creation/modification timestamps in upload directories using: find /path/to/uploads -type f -mtime -30 (adjust timeframe as needed)Affected if Recent executable files were uploaded to the environment
If InstaWP Connect version is below 0.1.0.39 and upload functionality is exposed, the environment is likely affected by this unrestricted file upload 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.
dbcve · scoped0.1.0.39
Restrict file uploads to safe, non-executable types (images, documents) with server-side validation including MIME type verification and file extension allowlists; store uploads outside webroot; implement proper authentication and authorization checks on upload endpoints.
0.1.0.39
- Log in to the WordPress admin dashboard where InstaWP Connect is installed
- Navigate to Plugins > InstaWP Connect
- Check if an update to version 0.1.0.39 or later is available
- If update available, click 'Update Now' to apply the security patch
- Verify the update was successful by checking the installed version number
- If automatic updates are not configured, manually download the updated plugin from the official WordPress repository or InstaWP and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Instawp Connect
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37228 — 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-37228 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