Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level WordPress account
-
DeliveryInject script into lightbox_class shortcode attribute
-
ExploitStore payload in testimonial view with thumbnail
-
ExecutionVictim loads page rendering thumbnail
-
ImpactScript executes in victim/admin browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with contributor-level access or above (PR:L) on a site running Strong Testimonials <=3.3.8. Exploitation is further constrained: the targeted testimonial view must contain at least one published testimonial that has a featured image AND have the lightbox wrapper enabled, because the vulnerable 'lightbox_class' output path is only reached when a thumbnail is rendered. No end-user interaction beyond a victim loading the injected page (UI:N); the stored script fires automatically when the thumbnail renders. These role and configuration prerequisites meaningfully limit real-world exploitability despite the network attack vector. |
| Impact | This is a genuine-but-modest-severity issue, not a top-tier priority. The CVSS 6.4 (Medium) reflects the real profile: network-reachable (AV:N) and low-complexity (AC:L), but gated behind contributor-level authentication (PR:L) and a scope change (S:C) with only Low confidentiality and integrity impact (C:L/I:L) - consistent with stored XSS that runs in a victim's browser rather than server-side compromise. No EPSS score, no CISA KEV listing, and no public POC are present in the provided intelligence, so exploitation status is 'no public exploit identified at time of analysis.' Wordfence reporting plus a concrete fix changeset (3699887) and vulnerable source lines confirm the flaw is real and patched. The practical risk is further limited by the requirement that the targeted testimonial view actually render a thumbnail (published testimonial + featured image + lightbox wrapper enabled), which narrows the exploitable surface. Net: a legitimate stored-XSS bug worth patching promptly on affected sites, but there is no signal of widespread or active exploitation. |
| Exploit ScenarioDerived | A malicious or compromised contributor-level user on a WordPress site running Strong Testimonials <=3.3.8 injects a script payload into the 'lightbox_class' shortcode attribute of a testimonial view that has a published testimonial with a featured image and the lightbox wrapper enabled. When any visitor or administrator loads a page that renders the thumbnail, the unsanitized attribute executes attacker JavaScript in their browser session. No public exploit code was identified at time of analysis, but the attribute-injection path is straightforward for anyone with the required role. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Authenticated attackers with contributor-level access can inject persistent JavaScript into WordPress sites running Strong Testimonials 3.3.8 or earlier through the 'lightbox_class' shortcode attribute, due to insufficient input sanitization and output escaping. Exploitation requires that the targeted testimonial view has at least one published testimonial with a featured image and the lightbox wrapper enabled, because the vulnerable code path is only reached when a thumbnail is rendered; the stored script then executes automatically when any user views the injected page. No public exploit code or active exploitation has been identified, and the CVSS score of 6.4 reflects a scope change with low confidentiality and integrity impact.
RemediationAI
Update the Strong Testimonials plugin to a version patched against this issue. A fix has been committed in the plugin repository (changeset 3699887), but a specific released version number beyond 3.3.8 has not been independently confirmed; check the plugin's changelog or the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/52a92e3c-cb64-4fc5-9248-6f4fc2a6a3cc?source=cve for the exact fixed version. As an interim compensating control, restrict contributor-level and higher WordPress accounts to trusted users only, since the injection requires such privileges; this may limit content workflows. Alternatively, disable the lightbox wrapper feature or avoid using testimonial views that render thumbnails with featured images, though this reduces plugin functionality. Review and remove any suspicious 'lightbox_class' attributes in existing shortcodes. No public exploit code is known, but role auditing and credential hygiene are advised.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a stored cross-site scripting (CWE-79) vulnerability in the Strong Testimonials WordPress plugin, caused by insufficient sanitization of the 'lightbox_class' shortcode attribute and lack of output escaping when the attribute is rendered. The plugin processes shortcodes to display testimonials, and when a view is configured with a lightbox wrapper and contains a published testimonial with a featured image, the thumbnail rendering path uses the unescaped class value. The specific affected code is in includes/functions-image.php (line 70), includes/class-strong-testimonials-view-shortcode.php (line 60), and includes/class-strong-testimonials-render.php (line 723) within version 3.3.8. The CPE cpe:2.3:a:wpchill:strong_testimonials:*:*:*:*:*:*:*:* confirms that all versions up to and including 3.3.8 are affected. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N indicates a network-based, low-complexity attack requiring low privileges (authenticated contributor or higher) with no user interaction beyond a victim loading the page, and a scope change due to the script executing in the context of other users.
Know when Strong Testimonials gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Contributor role gives PR:L; stored XSS executing in another origin/context yields S:C with C:L/I:L and no availability impact; UI:N since the payload fires on page render.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Strong Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'lightbox_class' Shortcode Attribute in all versions up to, and including, 3.3.8 due to insufficient input sanitization and output escaping. 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. Exploitation requires that the targeted testimonial view has at least one published testimonial with a featured image and the lightbox wrapper enabled, as the vulnerable code path is only reached when a thumbnail is rendered.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Strong Testimonials
View allStored XSS in the Strong Testimonials plugin before 2.40.1 for WordPress can result in an attacker performing malicious
The Strong Testimonials WordPress plugin before 3.1.12 does not validate and escape some of its Testimonial fields befor
Stored cross-site scripting in the Strong Testimonials WordPress plugin (all versions through 3.3.11) can let unauthenti
Cross-site scripting in the Strong Testimonials WordPress plugin (versions through 3.3.11) lets an authenticated attacke
Stored cross-site scripting in Strong Testimonials WordPress plugin up to version 3.2.21 allows authenticated contributo
Authenticated attackers holding only low-privilege WordPress accounts can abuse improperly enforced access controls in t
Auth. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor pat
Missing Authorization vulnerability in WP Chill Strong Testimonials strong-testimonials.1.16. Rated medium severity (CVS
The Strong Testimonials plugin for WordPress is vulnerable to unauthorized modification of data due to an improper capab
Cross-Site Request Forgery (CSRF) vulnerability in WPChill Strong Testimonials.1.10. Rated medium severity (CVSS 4.3), t
Missing authorization checks in the WP Chill Strong Testimonials WordPress plugin through version 3.3.12 allow an attack
EUVD-2026-82752
GHSA-frw6-hj49-2fr4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB