WordPress plugin
Stape Conversion Tracking security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 3 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High1
- Medium2
- Low0
All Stape Conversion Tracking vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Unauthenticated Server-Side Request Forgery <2.3.11Update to 2.3.11 | CVE-2026-118422 |
- High7.2Unauthenticated Server-Side Request Forgery
<2.3.11Update to 2.3.11
Stape Conversion Tracking: common questions
Does Stape Conversion Tracking have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Stape Conversion Tracking: 1 high, 2 medium. None are known to affect version null.
How do I check which version of Stape Conversion Tracking 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 Stape Conversion Tracking vulnerability?
CVE-2026-118422, published Nov 4, 2026: Stape Conversion Tracking < 2.3.11 - Unauthenticated Server-Side Request Forgery. Severity: High (CVSS 7.2).
Is any Stape Conversion Tracking vulnerability listed in CISA KEV?
No. None of the known Stape Conversion Tracking vulnerabilities is currently listed in the CISA KEV catalog.