Skip to content
Laskyr

Plugins · elasticpress · data as of 2026-11-04

Is ElasticPress safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (5.3.5)

As of 2026-11-04. 3 issues are on record for older versions; version 5.3.5 or newer fixes all of them that state a fix.

Latest version
5.3.5
Last updated
2026-09-10
Active installs
8,000+
Known issues on record
3
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.4+

A fast and flexible search and query engine for WordPress. — by 10up

What to do

  1. Update to the latest version (5.3.5). Anything older than 5.3.5 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get elasticpress --field=version shows what you run; wp plugin update elasticpress updates it.

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2026-62088 · published 2026-09-11

Information disclosure in ElasticPress (5.3.4 and older)

Affected
5.3.4 and older
Fixed in
5.3.5
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Insertion of Sensitive Information Into Sent Data vulnerability in 10up ElasticPress allows Retrieve Embedded Sensitive Data. This issue affects ElasticPress: from n/a through 5.3.4.

NVD CVE-2026-62088Patchstack advisory

medium 4.3 CVE-2024-35684 · published 2024-06-08

Cross-site request forgery (CSRF) in ElasticPress (5.1.1 and older)

Affected
5.1.1 and older
Fixed in
5.1.2
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in 10up ElasticPress elasticpress.This issue affects ElasticPress: from n/a through <= 5.1.1.

NVD CVE-2024-35684Patchstack advisoryPatchstack advisory

medium 4.3 CVE-2021-4405 · published 2023-07-01

Cross-site request forgery (CSRF) in ElasticPress (3.5.3 and older)

Affected
3.5.3 and older
Fixed in
3.5.4 *
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

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.

NVD CVE-2021-4405Wordfence advisoryCode change (fix)blog.nintechnet.comblog.nintechnet.comblog.nintechnet.comblog.nintechnet.com

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
ElasticPress vulnerability status badge
<a href="https://laskyr.com/plugins/elasticpress"><img src="https://laskyr.com/plugins/elasticpress/badge.svg" alt="ElasticPress vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit