Instawp ConnectWordPress extension · Instawp
CVE-2024-25918
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 InstaWP InstaWP Connect instawp-connect.This issue affects InstaWP Connect: from n/a through <= 0.1.0.8.
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 confidenceCode injection vulnerability in InstaWP Connect WordPress plugin affecting versions up to 0.1.0.8. The vulnerability allows attackers to inject and execute malicious code due to improper control of code generation, likely through unsanitized user input being used in dynamic code execution functions.
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.9CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate InstaWP Connect plugin directoryCheck your WordPress plugins folder (wp-content/plugins/) for a folder named 'instawp' or 'instawp-connect'Affected if The plugin folder exists in the WordPress installation
-
Identify installed plugin versionOpen the main plugin file (usually instawp-connect.php or instawp.php) and look for the 'Version' header in the plugin comment block, or check the version defined in the plugin's main PHP fileAffected if The version number found is less than 0.1.0.9
-
Verify plugin is activeCheck WordPress admin under Plugins > Installed Plugins, or query the wp_options table for 'active_plugins' option to see if instawp is in the list of active pluginsAffected if InstaWP Connect is installed and enabled on the site
You are affected if the InstaWP Connect plugin is installed, active, and its version is below 0.1.0.9, as this code injection vulnerability exists in all vulnerable versions of the plugin.
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.9
Update InstaWP Connect to the latest patched version immediately. If patching is not possible, disable the plugin and implement a web application firewall as a temporary measure to block exploitation attempts.
0.1.0.9
- Log in to the WordPress admin dashboard where InstaWP Connect is installed
- Navigate to Plugins > InstaWP Connect
- If an update is available, click 'Update Now' to upgrade to version 0.1.0.9
- Alternatively, navigate to Dashboard > Updates and apply any available updates
- After updating, verify the plugin version shows 0.1.0.9 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Instawp Connect
Scoped from the published advisory
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25918 — 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-25918 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