CVE-2024-13913
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 · uneditedThe InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.1.0.83. This is due to missing or incorrect nonce validation in the '/migrate/templates/main.php' file. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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 confidenceThe InstaWP Connect WordPress plugin versions up to 0.1.0.83 lack proper nonce validation in /migrate/templates/main.php, allowing unauthenticated attackers to trick administrators into executing malicious requests. Combined with the file inclusion capability, this CSRF flaw enables arbitrary PHP code execution on the server.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 versionNavigate to WordPress admin > Plugins > InstaWP Connect and read the version number from the plugin description, or inspect the main plugin file header in wp-content/plugins/instawp-connect/ for the 'Version' commentAffected if Installed version is 0.1.0.83 or lower, or the version cannot be determined (indicating an outdated installation)
-
Locate the affected PHP fileCheck if the file /migrate/templates/main.php exists within the InstaWP Connect plugin directory (typically wp-content/plugins/instawp-connect/migrate/templates/main.php)Affected if The file exists in the plugin directory, indicating the vulnerable code path is present
-
Inspect nonce validation in the affected fileOpen /migrate/templates/main.php and search for 'wp_verify_nonce' or 'nonce' verification around state-changing code sections (form submissions, API calls, or file operations)Affected if No wp_verify_nonce() or check_admin_referer() call is found before executing actions that modify state or include files
-
Confirm file inclusion capability is accessibleExamine the same file for functions that include or require PHP files (include, require, include_once, require_once) that could be manipulated through user-controlled parametersAffected if File inclusion functions exist without proper validation, allowing path traversal or user-controlled file inclusion
The environment is affected if InstaWP Connect plugin version 0.1.0.83 or lower is installed, the vulnerable file /migrate/templates/main.php exists, and the code lacks proper nonce validation before performing state-changing actions that include files.
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 dataAdd proper nonce verification using wp_verify_nonce() to all state-changing actions in the affected file, and update to the latest plugin version once available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13913 — 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-13913 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