WordPress plugin
Slickstream: Engagement and Conversions security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 2 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High0
- Medium2
- Low0
All Slickstream: Engagement and Conversions vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Cross-Site Request Forgery ≤2.0.3Update to 3.0.0 | CVE-2025-53273 | |
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting via slick-grid Shortcode ≤1.4.4Update to 2.0.0 | CVE-2024-10179 |
- Medium4.3Cross-Site Request Forgery
≤2.0.3Update to 3.0.0
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via slick-grid Shortcode
≤1.4.4Update to 2.0.0
Slickstream: Engagement and Conversions: common questions
Does Slickstream: Engagement and Conversions have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in Slickstream: Engagement and Conversions: 2 medium. None are known to affect version null.
How do I check which version of Slickstream: Engagement and Conversions I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Slickstream: Engagement and Conversions vulnerability?
CVE-2025-53273, published Jun 27, 2025: Slickstream <= 2.0.3 - Cross-Site Request Forgery. Severity: Medium (CVSS 4.3).
Is any Slickstream: Engagement and Conversions vulnerability listed in CISA KEV?
No. None of the known Slickstream: Engagement and Conversions vulnerabilities is currently listed in the CISA KEV catalog.