Search EverythingWordPress extension · Search Everything Project
CVE-2016-10917
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.6 for WordPress has SQL injection related to empty search strings, 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 confidenceThe search-everything WordPress plugin before version 8.1.6 contains a SQL injection vulnerability exploitable via empty search strings, allowing unauthenticated attackers to inject malicious SQL queries into the database.
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.6CVSS 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 Search Everything plugin filesCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'search-everything' or similar variant containing the Search Everything pluginAffected if The plugin folder exists in the WordPress installation
-
Identify the installed versionOpen the main plugin PHP file in the search-everything folder and locate the version string in the plugin header (e.g., 'Version: x.x.x' comment block) or query the wp_options table for the 'search_everything_version' optionAffected if The version retrieved is less than 8.1.6
-
Confirm plugin is activeQuery the WordPress database wp_options table for the 'active_plugins' option, or check via WordPress admin dashboard Plugins page, to determine if Search Everything is currently enabledAffected if The plugin is active and version is below 8.1.6
A user is affected if the Search Everything WordPress plugin is installed, active, and running a version lower than 8.1.6, which allows unauthenticated SQL injection via empty search strings.
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.6
Update the search-everything plugin to version 8.1.6 or later to remediate the SQL injection vulnerability.
Search Everything version 8.1.6
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Search Everything' plugin in the list
- Check if current version is below 8.1.6
- If vulnerable, click 'Update Now' next to Search Everything plugin
- Verify update completes successfully
- Confirm the installed version is 8.1.6 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Search Everything
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10917 — 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-2016-10917 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