CVE-2026-120683 · Package
NO FIX YET
The Real Testimonials WordPress plugin up to and including 4.1.0 does not sanitize the tpro_client_testimonial parameter, so unauthenticated visitors can submit testimonials containing scripts. Once an administrator approves the testimonial, the script runs in the browser of anyone who loads the affected page.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Real Testimonials plugin at version 4.1.0 or earlier where testimonials are published on pages that load the WordPress Interactivity runtime, such as a theme or block that enqueues @wordpress/interactivity. Exploitation needs an administrator to approve a submitted testimonial, so sites with no testimonial form or that do not use the plugin can skip it.
Not affected if no-interactivity-runtime, no-public-testimonial-form, plugin-not-installed
Who cares self-hosted, wordpress, wordpress-plugin
4.1.0 are affected.No fix yet, per the sources.
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_testimonial' 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. Successful exploitation requires an administrator to approve the pending testimonial through standard moderation and the target page to load the WordPress Interactivity runtime (e.g. a theme or block that enqueues @wordpress/interactivity).
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.