ElasticPress at a glance
- 9 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Sep 11, 2026.
- Ranked #2398 by popularity on WordPress.org (8,000+ active installs).
- The latest version is 5.3.6 (released Nov 11, 2026). The most recent security fix shipped in 5.3.5.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your ElasticPress version
Enter the ElasticPress version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “ElasticPress”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “ElasticPress”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (5.3.6). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known ElasticPress vulnerabilities
ElasticPress <= 5.3.4 - Unauthenticated Information Exposure
Information disclosure · CVE-2026-62088
Affected versions: ≤ 5.3.4
Fixed in: 5.3.5
Severity: Medium 5.3 · Disclosed Sep 11, 2026
ElasticPress <= 5.1.0 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2024-35684
Affected versions: ≤ 5.1.0
Fixed in: 5.1.1
Severity: Medium 4.3 · Disclosed Jun 6, 2024
webpack JS package <= 5.75.0 - Sandbox Bypass
Other weakness · CVE-2023-28154
Affected versions: ≤ 4.5.0
Fixed in: 4.5.1
Severity: High 8.3 · Disclosed Apr 11, 2023
simple-git < 3.15.0 - Remote Code Execution
Remote code execution · CVE-2022-25912
Affected versions: ≤ 4.4.0
Fixed in: 4.4.1
Severity: Critical 9.8 · Disclosed Dec 5, 2022
loader-utils (JS package) < 2.0.3 - Prototype Pollution
Other weakness · CVE-2022-37601
Affected versions: ≤ 4.3.1
Fixed in: 4.4.0
Severity: Medium 5.4 · Disclosed Oct 12, 2022
loader-utils (JS package) < 3.2.1 - Regular Expression Denial of Service
Other weakness · CVE-2022-37599
Affected versions: ≤ 4.3.1
Fixed in: 4.4.0
Severity: Low 3.7 · Disclosed Oct 11, 2022
terser (JS Package) < 5.14.2 - Denial of Service
Other weakness · CVE-2022-25858
Affected versions: ≤ 4.2.2
Fixed in: 4.3.0
Severity: Low 3.7 · Disclosed Jul 14, 2022
Moment.js <= 2.29.1 - Directory Traversal
Arbitrary file read or deletion
Affected versions: ≤ 4.1.0
Fixed in: 4.2.0
Severity: High 7.5 · Disclosed Apr 5, 2022
ElasticPress <= 3.5.3 - Cross-Site Request Forgery Bypass
Cross-site request forgery (CSRF) · CVE-2021-4405
Affected versions: ≤ 3.5.3
Fixed in: 3.5.4
Severity: Medium 4.3 · Disclosed Mar 1, 2021
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| ElasticPress <= 5.3.4 - Unauthenticated Information ExposureInformation disclosure · CVE-2026-62088 | ≤ 5.3.4 | 5.3.5 | Medium 5.3 | Sep 11, 2026 |
| ElasticPress <= 5.1.0 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2024-35684 | ≤ 5.1.0 | 5.1.1 | Medium 4.3 | Jun 6, 2024 |
| webpack JS package <= 5.75.0 - Sandbox BypassOther weakness · CVE-2023-28154 | ≤ 4.5.0 | 4.5.1 | High 8.3 | Apr 11, 2023 |
| simple-git < 3.15.0 - Remote Code ExecutionRemote code execution · CVE-2022-25912 | ≤ 4.4.0 | 4.4.1 | Critical 9.8 | Dec 5, 2022 |
| loader-utils (JS package) < 2.0.3 - Prototype PollutionOther weakness · CVE-2022-37601 | ≤ 4.3.1 | 4.4.0 | Medium 5.4 | Oct 12, 2022 |
| loader-utils (JS package) < 3.2.1 - Regular Expression Denial of ServiceOther weakness · CVE-2022-37599 | ≤ 4.3.1 | 4.4.0 | Low 3.7 | Oct 11, 2022 |
| terser (JS Package) < 5.14.2 - Denial of ServiceOther weakness · CVE-2022-25858 | ≤ 4.2.2 | 4.3.0 | Low 3.7 | Jul 14, 2022 |
| Moment.js <= 2.29.1 - Directory TraversalArbitrary file read or deletion | ≤ 4.1.0 | 4.2.0 | High 7.5 | Apr 5, 2022 |
| ElasticPress <= 3.5.3 - Cross-Site Request Forgery BypassCross-site request forgery (CSRF) · CVE-2021-4405 | ≤ 3.5.3 | 3.5.4 | Medium 4.3 | Mar 1, 2021 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 11, 2026.
Most common weaknesses in ElasticPress
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
Remote code execution
1 issue
An attacker can run code of their choice on your server. This is the most dangerous kind: it usually means a full takeover of the site.
Frequently asked questions
Is ElasticPress safe to use?
ElasticPress is a well-known plugin with 8,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (5.3.6) and turn on automatic updates.
How do I find which version of ElasticPress my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.