HomeWordPress vulnerabilitiesElasticPress
ElasticPress vulnerabilities
ElasticPress has 2 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 2
- Active installs
- 8,000+
- Latest version
- 5.3.6
- Last updated
- 11 Nov 2026
- Most recent
- 21 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-116518 | High 7.2 | Up to 5.3.5 | Fixed in a later version (latest 5.3.6) | 1 d ago |
| Cross-site request forgery (CSRF) CVE-2021-4405 | Medium 4.3 | Up to 3.5.3 | Fixed in a later version (latest 5.3.6) | 1 Jul 2023 |
Read the published descriptions
- CVE-2026-116518, 21 Nov 2026
- 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. CVE record
- CVE-2021-4405, 1 Jul 2023
- The ElasticPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.5.3. This is due to missing or incorrect nonce validation on the epio_send_autosuggest_allowed() function. This makes it possible for unauthenticated attackers to send allowed parameters for autosuggest to elasticpress[.]io via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
What to do if you run ElasticPress
If you run ElasticPress, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new ElasticPress vulnerabilities
Free. We email you when a new vulnerability is published for ElasticPress, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.