Search EverythingWordPress extension · Search Everything Project
CVE-2017-18571
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 search-everything plugin before 8.1.7 for WordPress has SQL injection related to WordPress 4.7.x, a different vulnerability than CVE-2014-2316.
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 confidenceSQL injection vulnerability in the search-everything WordPress plugin before version 8.1.7 allows unauthenticated attackers to inject malicious SQL queries through search parameters, affecting WordPress 4.7.x installations.
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
Search EverythingWordPress extension
< 8.1.7CVSS 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.0/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.
-
Locate the search-everything plugin filesAccess your WordPress installation via file system or FTP. Navigate to /wp-content/plugins/ and check if a folder named 'search-everything' exists.Affected if The plugin folder is present in the plugins directory.
-
Identify the installed plugin versionIf the plugin is installed, open the main plugin file (usually search-everything.php) and locate the version declaration in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.Affected if The version number found is lower than 8.1.7.
-
Confirm WordPress core versionIn the WordPress admin dashboard, go to Dashboard > Updates or check the wp-includes/version.php file to determine the WordPress core version.Affected if WordPress 4.7.x is running (versions 4.7.0 through 4.7.x).
-
Verify search functionality is accessibleConfirm that the search feature using the search-everything plugin is publicly accessible. This typically applies to any frontend search form on the site.Affected if The search functionality is enabled and accessible to unauthenticated users (which is the default configuration).
You are affected if the search-everything plugin is installed with a version below 8.1.7 on a WordPress 4.7.x site with search functionality enabled.
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 · scoped8.1.7
Upgrade the search-everything plugin to version 8.1.7 or later to remediate the SQL injection vulnerability.
Search Everything version 8.1.7
- Backup your WordPress site database and files before making any changes
- Navigate to the WordPress admin dashboard > Plugins section
- Locate the Search Everything plugin
- Update the Search Everything plugin to version 8.1.7 or later
- Verify the plugin version has been updated successfully in the Installed Plugins list
- Clear any caching mechanisms if used
- Test search functionality to ensure the plugin operates correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Search Everything
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18571 — 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-2017-18571 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