Skip to main content
Menu
CVEs

CVE

Search Everything missing authorization in AJAX search exposes passwords

CVE-2026-120564Published Updated

6.5MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Search Everything plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 8.1.9 via the search_everything AJAX action. The handler registered at wp_ajax_search_everything performs no capability check, no ownership check, and no nonce verification before running a WP_Query over $_GET['s'] and returning the raw WP_Post objects — including the post_password field — as JSON. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract cleartext passwords for every password-protected post on the site and, when the plugin's draft/attachment/metadata search options are enabled by an administrator, to read draft and pending post contents they otherwise have no capability to view.

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120564 (Search Everything <= 8.1.9 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via 's' Parameter via…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120564 (entry last updated 2026-11-18):
Affected:
- sovrn Search Everything: through 8.1.9
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120564 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120564 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bcd413ae-2cee-47a3-9e75-0b49c2fa9a2b?source=cve
- https://plugins.trac.wordpress.org/browser/search-everything/tags/8.1.9/search-everything.php#L907
- https://plugins.trac.wordpress.org/browser/search-everything/tags/8.1.9/search-everything.php#L850
- https://plugins.trac.wordpress.org/browser/search-everything/tags/8.1.9/search-everything.php#L856
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120564
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120564"}.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated
  4. First seen by cve.now

Affected versions

  • sovrn Search Everything

    through 8.1.9

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-120564

Is CVE-2026-120564 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120564?

Search Everything: through 8.1.9.Source: cve.now feed data

More CVEs