ElasticPress unauthenticated stored XSS via orderby parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
Unauthenticated attackers can reach the ElasticPress WordPress plugin remotely through a crafted 'orderby' parameter on a frontend page request, storing a script that runs in the browser of an administrator who later opens the Status Report page and expands the Failed Queries panel. The injected script can then act with that administrator's access to the site.
Written by a model
Original description
The ElasticPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'orderby' parameter in all versions up to, and including, 5.3.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is stored in the ep_query_log transient for up to 24 hours after a single unauthenticated frontend GET request, and only fires when an administrator subsequently opens the Status Report page and expands the Failed Queries panel.
What to do
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-116518 (ElasticPress <= 5.3.5 - Unauthenticated Stored Cross-Site Scripting via 'orderby' Parameter), 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-116518 (entry last updated 2026-11-21):
Affected:
- 10up ElasticPress: through 5.3.5
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116518 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116518 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/4e3af605-3f95-4dd2-a028-a38519afc296?source=cve
- https://plugins.trac.wordpress.org/browser/elasticpress/tags/5.3.5/assets/js/status-report/components/reports/report/value.js#L32
- https://plugins.trac.wordpress.org/browser/elasticpress/tags/5.3.5/includes/classes/StatusReport/FailedQueries.php#L76
- https://plugins.trac.wordpress.org/browser/elasticpress/tags/5.3.5/includes/classes/StatusReport/FailedQueries.php#L165
- https://plugins.trac.wordpress.org/browser/elasticpress/tags/5.3.5/includes/utils.php#L862
- https://plugins.trac.wordpress.org/browser/elasticpress/tags/5.3.5/includes/classes/QueryLogger.php#L312
- https://plugins.trac.wordpress.org/browser/elasticpress/tags/5.3.5/includes/classes/Indexable/Post/Post.php#L1218
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3796839%40elasticpress&new=3796839%40elasticpress
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-116518
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-116518"}.Affected versions
- 10up ElasticPressthrough 5.3.5
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 10
Questions about CVE-2026-116518
Is CVE-2026-116518 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-116518?
ElasticPress: through 5.3.5.
Source: cve.now feed data
Related
- CVE-2026-62088WordPress ElasticPress plugin <= 5.3.4 - Sensitive Data Exposure vulnerability
- CVE-2024-35684WordPress ElasticPress plugin <= 5.1.1 - Cross Site Request Forgery (CSRF) vulnerability
- CVE-2021-4405ElasticPress <= 3.5.3 - Cross-Site Request Forgery Bypass
- CVE-2026-94077WordPress Safe SVG plugin <= 2.5.0 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-5028Eight Day Week Print Workflow <= 1.2.6 - Authenticated (Subscriber+) SQL Injection via 'title' Parameter
- CVE-2026-25311WordPress Autoshare for Twitter plugin <= 2.3.1 - Broken Access Control vulnerability
No corrections so far. Something wrong on this page? Report an error.