LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10917: The search-everything plugin before 8.1.6 for WordPress has SQL injection related to empty search strings,...

The search-everything plugin before 8.1.6 for WordPress has SQL injection related to empty search strings, a different vulnerability than CVE-2014-2316.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a SQL injection flaw in the WordPress Search Everything plugin before version 8.1.6. SQL injection can expose or alter database data, but the provided sources do not give a CVSS score, exploit evidence, or detailed impact. Treat it as a plugin hygiene and exposure issue until vendor details are confirmed.

Executive priority

Prioritize remediation for internet-facing WordPress sites running Search Everything below 8.1.6. Business urgency is constrained by incomplete severity data, but SQL injection in a CMS plugin can create meaningful data risk if reachable.

Technical view

Search Everything before 8.1.6 is reported vulnerable to SQL injection related to empty search strings. The record states this is distinct from CVE-2014-2316. The source bundle does not provide affected CPEs, CWE mapping, CVSS metrics, authentication requirements, exploit prerequisites, or patch notes beyond the version boundary.

Likely exposure

Likely limited to WordPress sites that have the Search Everything plugin installed below version 8.1.6. Public exposure depends on whether the plugin is active and its search behavior is reachable. The source bundle does not confirm affected configurations beyond the plugin version range.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked as CISA KEV. No public exploit status, attacker requirements, or real-world campaign details are provided. Do not assume exploitation without additional source evidence.

Researcher notes

Evidence is sparse. The CVE description gives the vulnerable plugin and version boundary but lacks root-cause detail, affected code paths, privilege context, and impact metrics. Further validation should stay defensive and focus on version confirmation, vendor changelog review, and environmental exposure.

Mitigation direction

  • Inventory WordPress sites for Search Everything plugin usage.
  • Upgrade Search Everything to version 8.1.6 or later where feasible.
  • If upgrade is unavailable, check current vendor guidance before choosing compensating controls.
  • Disable or remove unused vulnerable plugin installations.
  • Review web and database logs for unusual search-related activity.

Validation and detection

  • Confirm installed Search Everything plugin version on each WordPress site.
  • Verify whether the plugin is enabled and used in production.
  • Check vendor release history for version 8.1.6 remediation details.
  • Review security monitoring for anomalous search requests and database errors.
  • Document any sites unable to upgrade for risk acceptance review.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-10917 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.