WordPress Strong Testimonials Plugin Stored XSS via Custom Fields

The Strong Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'platform_user_photo' Custom Field in all versions up to, and including, 3.3.11 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that an administrator has added custom text fields named 'platform' and 'platform_user_photo' to a public testimonial submission form, as the plugin does not reserve those internal metadata keys.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Strong Testimonials WordPress plugin contains a stored cross-site scripting (XSS) vulnerability in custom field handling, specifically the 'platform_user_photo' field. Attackers can inject malicious JavaScript that persists in the database and executes whenever any user views an affected page. With a CVSS score of 7.2, this represents a high-severity risk affecting all versions up to 3.3.11. Because exploitation requires only that an administrator configured custom text fields named 'platform' and 'platform_user_ph', the attack surface is broad across WordPress installations using this plugin—particularly those hosting testimonials, reviews, or user-generated content where custom fields are leveraged.

Casky's 323 matching skills leverage Claude's extended reasoning to detect the attack patterns underlying this CVE by mapping to MITRE ATT&CK techniques TA0001 (reconnaissance) and TA0043 (reconnaissance via web scraping and content analysis). Practitioners using Casky would identify findings related to CWE-79 violations through pattern recognition of insufficient input sanitization and output escaping in plugin code. The platform would flag instances where untrusted user input flows into custom field values without proper HTML encoding, then surfaces in page rendering contexts. Security teams would see detection indicators highlighting stored payload persistence, DOM execution paths, and scenarios where unauthenticated attackers craft malicious testimonial submissions—enabling proactive patching and input validation remediation before exploitation occurs in production environments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-96650.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-96650

Casky has 323 skills that investigate the attack patterns behind CVE-2026-96650. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn