Stape Conversion Tracking · Security record
Is Stape Conversion Tracking safe?
No known vulnerability affects the current version (2.3.11). 3 issues were found in earlier versions and fixed, the latest disclosed on Oct 23, 2026.
Checked 4 days ago against the WPVulnerability database, for version 2.3.11.
How it’s looked after
- Last release
- Oct 28, 2026 (1 week ago)
- Releases in the last year
- 23
- Tested up to
- WordPress 7.1.0
- Active installs
- 10K+
3 known vulnerabilities
- 1 medium
- 2 not rated
None affects the current version.
Disclosed each year
- 20221
- 20241
- 20261
Every known vulnerability in Stape Conversion Tracking
Newest first, with any that affect the current version at the top.
Fixed in 2.1.48 · CVE-2026-55826 · Oct 23, 2026 · CVE
Fixed in 2.1.20 · CVE-2024-8712 · Sep 27, 2024 · Wordfence
Fixed in 1.1.2 · Jun 22, 2022 · Wordfence
Questions about Stape Conversion Tracking’s security
Is Stape Conversion Tracking safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Stape Conversion Tracking updated: most attacks target sites that haven’t updated.
Does Stape Conversion Tracking have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 3 older issues, fixed in earlier versions, so keep Stape Conversion Tracking up to date.
Is Stape Conversion Tracking still maintained?
Yes. Its last release was 1 week ago. No support threads were opened in the last two months.
Is Stape Conversion Tracking compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.0, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.