CVE-2026-57628
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 · uneditedAdministrator SQL Injection in WP All Import <= 4.0.1 versions.
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 confidenceSQL injection vulnerability in WP All Import plugin for WordPress allows authenticated administrators to inject malicious SQL queries through unsanitized input, potentially enabling data exfiltration or database manipulation.
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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
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 WP All Import plugin is installedLog into WordPress admin, navigate to Plugins > Installed Plugins, and search for 'WP All Import' or check the wp-content/plugins directory for the wp-all-import folderAffected if The plugin is present in the WordPress installation
-
Identify the installed version of WP All ImportIn WordPress admin, go to Plugins > Installed Plugins, find WP All Import, and note the version number displayed in the plugin row. Alternatively, open the main plugin file (usually wp-all-import.php) and look for the 'Version' header in the file commentsAffected if The installed version matches or falls within the affected version range for this CVE
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that WP All Import shows as 'Active' rather than 'Inactive'Affected if The plugin is currently active in the WordPress installation
-
Verify admin user accessNavigate to Users > All Users in WordPress admin and review which accounts have the Administrator role, or query the wp_usermeta table for capability 'administrator'Affected if There are administrator accounts present (the SQL injection can be exploited by any authenticated administrator)
You are affected if WP All Import is installed, active, and running a version within the CVE-affected range, regardless of how trusted your administrators are.
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 · scopedUpgrade WP All Import to the latest version immediately; if patching is not possible immediately, restrict admin access to only trusted users and implement additional input validation at the web application firewall level.
WP All Import version 4.0.2 or later (latest stable release)
- Log in to the WordPress admin dashboard.
- Navigate to Plugins > Installed Plugins.
- Locate WP All Import and check the current version; if it is <=4.0.1, the site is vulnerable.
- Update the plugin to the latest available version (version 4.0.2 or later) using the WordPress plugin update mechanism.
- After the update, verify the new version is installed and test that the plugin’s import functionality works as expected.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57628 — 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-2026-57628 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