Plugins · wp-meteor · data as of 2026-11-04
Is WP Meteor Website Speed Optimization Addon safe? Known vulnerabilities and latest version
- Latest version
- 3.4.19
- Last updated
- 2026-10-03
- Active installs
- 20,000+
- Known issues on record
- 4
- Unpatched in latest
- 0
- Tested up to WP
- 7.0.8 · PHP 5.6+
2x-5x improvement in your Page Speed score. A completely new way of optimizing your page speed. — by Aleksandr Guidrevitch
What to do
- Update to the latest version (3.4.19). Anything older than 3.4.19 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- 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 wp-meteor --field=version shows what you run; wp plugin update wp-meteor updates it.
Check your version
Known vulnerabilities
4 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.
high 7.2 CVE-2026-96572 · published 2026-10-10
Stored cross-site scripting (XSS) in WP Meteor Website Speed Optimization Addon (3.4.18 and older)
- Affected
- 3.4.18 and older
- Fixed in
- 3.4.19 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Meteor Website Speed Optimization Addon plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up to, and including, 3.4.18 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 payload is delivered via the comment author name field, which must clear WordPress's comment moderation workflow before being displayed, though this represents a display prerequisite rather than any sanitization control.
NVD CVE-2026-96572Wordfence advisoryCode change (fix)Plugin source
medium 6.1 CVE-2026-2902 · published 2026-04-29
Stored cross-site scripting (XSS) in WP Meteor Website Speed Optimization Addon (3.4.16 and older)
- Affected
- 3.4.16 and older
- Fixed in
- 3.4.17 *
- 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 WP Meteor Website Speed Optimization Addon plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'frontend_rewrite' function's 'WPMETEOR[N]WPMETEOR' placeholder content in all versions up to, and including, 3.4.16 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.
NVD CVE-2026-2902Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2024-6553 · published 2024-07-24
Information disclosure in WP Meteor Website Speed Optimization Addon (3.4.3 and older)
- Affected
- 3.4.3 and older
- Fixed in
- 3.4.4 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Meteor Website Speed Optimization Addon plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.3.This is due to the plugin utilizing wpdesk and leaving test files with display_errors on. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.
high 8.8 CVE-2023-26543 · published 2023-11-13
Cross-site request forgery (CSRF) in WP Meteor Website Speed Optimization Addon (3.1.4 and older)
- Affected
- 3.1.4 and older
- Fixed in
- 3.1.5
- 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 Aleksandr Guidrevitch WP Meteor Website Speed Optimization Addon plugin <= 3.1.4 versions.
Recent activity
- 2026-10-03 — latest release on wordpress.org (3.4.19).
- 2026-10-10 — Stored cross-site scripting (XSS) disclosed (CVE-2026-96572), fixed in 3.4.19.
- 2026-04-29 — Stored cross-site scripting (XSS) disclosed (CVE-2026-2902), fixed in 3.4.17.
- 2024-07-24 — Information disclosure disclosed (CVE-2024-6553), fixed in 3.4.4.
Get an email when WP Meteor Website Speed Optimization Addon has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WP Meteor Website Speed Optimization Addon (wp-meteor) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (2) · Sensitive data exposure (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-meteor (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-meteor"><img src="https://laskyr.com/plugins/wp-meteor/badge.svg" alt="WP Meteor Website Speed Optimization Addon vulnerability status"></a>