CVE-2026-120685 json
Real Testimonials <= 4.1.0 - Unauthenticated Stored Cross-Site Scripting via JPEG IPTC Caption + '[gallery]' Shortcode Chain
published 4d ago modified 4d ago also EUVD-2026-119153
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
The Real Testimonials – Testimonial Slider, Collect Customer Reviews and Video Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tpro_client_image (JPEG IPTC caption) + tpro_client_testimonial ([gallery] shortcode)' parameter in all versions up to, and including, 4.1.0 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. This requires an administrator to have the display block configured with the Strip All HTML Tags option disabled, which is the plugin's native setting for rendering formatted testimonial content, and to have approved the submitted testimonials.
Is CVE-2026-120685 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4d ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- shapedplugin Real Testimonials – Testimonial Slider, Collect Customer Reviews and Video Testimonials
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/756c203e-8fbe-46f0-8ae7-a3f2d005cd6f?source=cve
- plugins.trac.wordpress.org /browser/testimonial-free/tags/4.1.0/src/Blocks/Templates/template-parts/testimonial-content.php#L34
- plugins.trac.wordpress.org /browser/testimonial-free/tags/4.1.0/src/Blocks/API/APIHelper.php#L50
- plugins.trac.wordpress.org /browser/testimonial-free/tags/4.1.0/src/Blocks/API/APIHelper.php#L151
- plugins.trac.wordpress.org /browser/testimonial-free/tags/4.1.0/src/Blocks/API/ManageAPI.php#L352
- plugins.trac.wordpress.org /browser/testimonial-free/tags/4.1.0/src/Blocks/Includes/TestimonialQuery.php#L240
- plugins.trac.wordpress.org /changeset/3781836/testimonial-free
- plugins.trac.wordpress.org /changeset/3781836/testimonial-free/trunk/src/Blocks/Templates/template-parts/testimonial-content.php
Sources
- CVE List CVE-2026-120685
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.