CVE-2026-3239
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Strong Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's testimonial_view shortcode in all versions up to, and including, 3.2.21 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Strong Testimonials WordPress plugin versions up to 3.2.21 contain a stored XSS vulnerability in the testimonial_view shortcode. Authenticated attackers with contributor-level permissions can inject arbitrary JavaScript via unsanitized shortcode attributes, which executes when other users view pages containing the injected shortcode.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Strong Testimonials plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Strong Testimonials' in the listAffected if The plugin is installed and active
-
Check installed plugin versionIn Plugins list, click on the Strong Testimonials plugin to view version details, or check the plugin files in /wp-content/plugins/strong-testimonials/ for a version fileAffected if Version is 3.2.21 or lower (the vulnerability affects versions up to and including 3.2.21)
-
Identify pages using testimonial_view shortcodeIn WordPress admin, go to Pages or Posts and search for [testimonial_view] in content, or use a plugin/site search to find all instances of the shortcodeAffected if Any page or post contains the testimonial_view shortcode
-
Inspect shortcode attributes for unsanitized inputView the source or edit affected pages and examine all attributes in [testimonial_view] shortcode tags (such as view_id, category, etc.) for unusual characters or script tagsAffected if Shortcode contains unsanitized attributes that could contain JavaScript (quotes, <script> tags, javascript: URLs, or event handlers)
-
Check user role permissionsGo to Strong Testimonials > Settings > Permissions (or similar) to see which roles can create or edit testimonials and shortcodesAffected if Contributor-level or higher users have permission to use the testimonial_view shortcode
You are affected if the Strong Testimonials plugin version is 3.2.21 or lower AND pages on your site use the testimonial_view shortcode that could contain unsanitized attributes from contributor-level users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Strong Testimonials plugin to version 3.2.22 or later, which includes proper input sanitization and output escaping for shortcode attributes. Until patched, restrict contributor-level access and review existing pages using the testimonial_view shortcode.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3239 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data