Strong TestimonialsWordPress extension · Wpchill
CVE-2023-26013
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in WPChill Strong Testimonials plugin <= 3.0.2 versions.
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 confidenceStored XSS vulnerability in WPChill Strong Testimonials plugin allows authenticated users with contributor-level permissions or higher to inject malicious JavaScript code into testimonial submissions. When other users or administrators view these testimonials in the WordPress admin dashboard or on the frontend, the injected script executes, potentially leading to session hijacking, credential theft, or administrative actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Strong TestimonialsWordPress extension
<= 3.0.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 installedNavigate to WordPress admin > Plugins and look for 'Strong Testimonials' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn Plugins list, click on the plugin name or view details to see the installed version number. Compare to 3.0.2Affected if The installed version number is 3.0.2 or lower (e.g., 3.0.1, 3.0.0, 2.x)
-
Confirm plugin is activeIn WordPress admin > Plugins, check if Strong Testimonials shows 'Active' statusAffected if The plugin is active and not deactivated
-
Check if testimonial submission form existsVisit any page on the site where a Strong Testimonials submission form may be present, or check plugin settings for form shortcode/statesAffected if A testimonial submission form is published and accessible, or the submission feature is enabled in plugin settings
If the Strong Testimonials plugin is installed, active, at version 3.0.2 or lower, and has a submission form enabled, the environment is affected by this stored XSS vulnerability.
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 a version newer than 3.0.2. Until the patch is applied, disable the plugin or implement output encoding and input validation as a compensating control.
Fix this in Strong Testimonials
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26013 — 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-2023-26013 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