ElasticPress through 5.3.5 stores unauthenticated input shown to admins in Failed Queries, fixed in 5.3.6
Identifiers: CVE-2026-116518 · GHSA-6hx4-m9fj-4m2q
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
ElasticPress, the WordPress plugin with slug elasticpress from 10up, is affected through version 5.3.5 inclusive under CVE-2026-116518. Unauthenticated input can be stored by the affected logging path and later rendered when an administrator opens the plugin's Status Report and expands the Failed Queries section. 10up released 5.3.6 on November 11, 2026 and its release notes describe the matching fix. Wordfence Intelligence disclosed the issue on November 20, 2026 and the CVE record was published on November 21. Patchstack lists the same affected and fixed versions and refers to Wordfence.
Impact
Stored cross-site scripting here means script running in an administrator's browser within the affected site's context. The effect stays within that browser session and the privileges of the signed-in administrator. It does not by itself amount to server-side code execution or evidence that site content was breached. The practical impact depends on an administrator opening the affected report. No reviewed advisory establishes real-world exploitation or compromise of any particular site.
Who is affected
Applies to sites running ElasticPress 5.3.5 or earlier. Two steps are involved. Unsafe input is first stored in the plugin's failed-query log by the affected logging path. An administrator later opens the Status Report and expands the Failed Queries section, where the stored entry is rendered. A normal visitor viewing search results is not exposed by that step alone.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| ElasticPress | <=5.3.5 | 5.3.6 |
Exploitation evidence
Exploitation not established. No reviewed advisory from 10up, Wordfence Intelligence or Patchstack reports observed exploitation or compromise of a specific site. The disclosed path requires an administrator to open the affected report after an unsafe entry has been stored.
Actions
- Confirm the installed plugin is ElasticPress (slug elasticpress) and record the exact version shown on the Plugins screen.
- Take a full backup, update to 5.3.6 or a newer patched release, then confirm site search returns expected results for a few benign test queries and that the Status Report opens without errors.
- Until the update is applied, avoid expanding the Failed Queries section as a temporary risk reduction. This limits one exposure point but does not replace patching.
- If there is any sign of abuse, have a maintainer review the plugin's stored failed-query logs and recent administrator activity rather than relying on the update alone.
Unknowns
- The exact ElasticPress version installed on any given site.
- Whether malicious entries were stored in the failed-query log before the update.
- No reviewed source reports real-world exploitation, but absence of reports is not proof that none occurred.
Sources
- Wordfence Intelligence https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/elasticpress/elasticpress-535-unauthenticated-stored-cross-site-scripting-via-orderby-parameter
- 10up https://github.com/10up/ElasticPress/releases/tag/5.3.6
- 10up https://github.com/10up/ElasticPress/security/advisories/GHSA-6hx4-m9fj-4m2q
- Patchstack https://patchstack.com/database/wordpress/plugin/elasticpress/vulnerability/wordpress-elasticpress-plugin-5-3-5-unauthenticated-stored-cross-site-scripting-vulnerability
- CVE Program, assigned by Wordfence https://cveawg.mitre.org/api/cve/CVE-2026-116518
Change history
- — Published: November 22, 2026: Brief created from the 10up 5.3.6 release notes, the Wordfence Intelligence disclosure and the Patchstack entry. Affected through 5.3.5, fixed in 5.3.6. No evidence of exploitation found in the reviewed sources.