CVE-2026-116518
Deferred Deferred - Pending Action

Stored XSS in ElasticPress WordPress Plugin

Vulnerability report for CVE-2026-116518, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
10up ElasticPress From 0 (inc) to 5.3.5 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The ElasticPress plugin for WordPress has a stored cross-site scripting (XSS) vulnerability in the 'orderby' parameter. This flaw allows unauthenticated attackers to inject malicious scripts into pages. The payload is stored in the ep_query_log transient for up to 24 hours after a single unauthenticated GET request and executes when an administrator views the Status Report page and opens the Failed Queries panel.

Detection Guidance

Check WordPress sites with ElasticPress 5.3.5 or earlier for the 'orderby' parameter in requests. Inspect the ep_query_log transient in the database for suspicious scripts. Review server logs for unauthenticated GET requests targeting ElasticPress endpoints.

Impact Analysis

An attacker could steal sensitive data like cookies or session tokens, perform actions on behalf of users, or deface websites. Since the payload persists for 24 hours, even a single unauthenticated request could lead to repeated exploitation. Administrators are particularly at risk as the script executes when they access the Status Report page.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection principles or HIPAA's security requirements. If exploited, it may result in data breaches, triggering mandatory breach notifications and potential fines under these regulations.

Mitigation Strategies

Update ElasticPress to the latest version. Remove any unauthorized scripts from the ep_query_log transient. Monitor admin dashboard access and failed query panels for unexpected activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-116518. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...