Strong Testimonials · Security record
Is Strong Testimonials safe?
No known vulnerability affects the current version (3.3.17). 28 issues were found in earlier versions and fixed, the latest disclosed on Oct 22, 2026.
Checked 3 days ago against the WPVulnerability database, for version 3.3.17.
How it’s looked after
- Last release
- Nov 2, 2026 (6 days ago)
- Releases in the last year
- 23
- Tested up to
- WordPress 7.1.4
- Support resolved
- 2 of 2 threads in two months
- Active installs
- 80K+
28 known vulnerabilities
- 3 high
- 18 medium
- 7 not rated
None affects the current version.
Disclosed each year
- 20182
- 20202
- 20211
- 20233
- 20243
- 20255
- 202610
Every known vulnerability in Strong Testimonials
Newest first, with any that affect the current version at the top.
Fixed in 3.3.16 · CVE-2026-114706 · Oct 22, 2026 · Wordfence
Fixed in 3.3.13 · CVE-2026-107435 · Oct 21, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 3.3.15 · CVE-2026-112843 · Oct 19, 2026 · Wordfence
Fixed in 3.3.13 · CVE-2026-107436 · Oct 18, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 3.3.13 · CVE-2026-110371 · Oct 15, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 3.3.13 · CVE-2026-109897 · Oct 15, 2026 · Wordfence
Fixed in 3.3.12 · CVE-2026-96650 · Sep 30, 2026 · Wordfence
Fixed in 3.3.12 · CVE-2026-97286 · Sep 17, 2026 · Wordfence
- medium
Authenticated (Contributor+) Stored Cross-Site Scripting via 'lightbox_class' Shortcode Attribute
Fixed in 3.3.9 · CVE-2026-92622 · Apr 7, 2026 · Wordfence
Fixed in 3.2.22 · CVE-2026-3239 · Apr 7, 2026 · Wordfence
Fixed in 3.2.19 · CVE-2025-14426 · Dec 29, 2025 · Wordfence
- medium
Missing Authorization
Fixed in 3.2.21 · CVE-2026-24957 · Dec 28, 2025 · Wordfence
Fixed in 3.2.17 · CVE-2025-11268 · Nov 5, 2025 · Wordfence
Fixed in 3.2.12 · CVE-2025-7367 · Jul 14, 2025 · Wordfence
- medium
Missing Authorization
Fixed in 3.2.4 · CVE-2025-26975 · Feb 23, 2025 · Wordfence
- medium
Missing Authorization
Fixed in 3.1.17 · CVE-2024-47362 · Sep 30, 2024 · Wordfence
Fixed in 3.1.13 · CVE-2023-6491 · Jun 6, 2024 · Wordfence
Fixed in 3.1.12 · CVE-2024-3261 · Apr 3, 2024 · Wordfence
Fixed in 3.1.11 · CVE-2023-52123 · Dec 28, 2023 · Wordfence
Fixed in 3.0.3 · CVE-2023-26013 · Feb 21, 2023 · Wordfence
Fixed in 3.0.3 · CVE-2022-4717 · Jan 10, 2023 · Wordfence
Fixed in 2.51.3 · Jun 30, 2021 · Wordfence
Fixed in 2.40.1 · Feb 1, 2020 · Patchstack
Fixed in 2.40.1 · CVE-2020-8549 · Feb 1, 2020 · Wordfence
Fixed in 2.31.5 · Aug 9, 2018 · Patchstack
Fixed in 2.31.5 · Jul 24, 2018 · Wordfence
Fixed in 2.51.3 · WPScan
Fixed in 2.31.5 · WPScan
Questions about Strong Testimonials’s security
Is Strong Testimonials safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Strong Testimonials updated: most attacks target sites that haven’t updated.
Does Strong Testimonials have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 28 older issues, fixed in earlier versions, so keep Strong Testimonials up to date.
Is Strong Testimonials still maintained?
Yes. Its last release was 6 days ago. Its authors resolved 2 of the 2 support threads opened in the last two months.
Is Strong Testimonials compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, 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.