Swift Performance Lite
swift-performance-lite · plugin
Known security vulnerabilities for Swift Performance Lite. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
3 exploitable without logging in · 2 with public exploit code · latest Oct 21, 2026
Before you install
Use with care
- 2 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 2.3.7.6 · last updated Nov 9, 2026 · 6K+ installs
wordpress.org status checked on Nov 11, 2026
Vulnerabilities
- High 8.1
CVE-2024-10516unauthenticated≤ 2.3.7.1
Swift Performance Lite <= 2.3.7.1 - Unauthenticated Local PHP File Inclusion via 'ajaxify'
- Medium 6.8
CVE-2026-110651author+→ 2.3.7.4
Swift Performance Lite < 2.3.7.4 - Author+ SQLi via Image Optimizer
- Medium 5.4
CVE-2024-3722subscriber+≤ 2.3.6.18
Swift Performance Lite <= 2.3.6.18 - Incorrect Authorization to Authenticated (Subscriber+) Settings Modification
- Medium 4.3
CVE-2024-37511unauthenticated · needs a click≤ 2.3.6.20
WordPress Swift Performance Lite plugin <= 2.3.6.20 - Cross Site Request Forgery (CSRF) vulnerability
- Medium 4.3
CVE-2023-6289unauthenticated→ 2.3.6.15
Swift Performance Lite <= 2.3.6.14 - Unauthenticated Configuration Export
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.