CVE-2026-1095
Stored XSS in Canto Testimonials WordPress Plugin via 'fx' Attribute
Publication date: 2026-01-24
Last updated on: 2026-01-24
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | canto_testimonials | to 1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1095 is a Stored Cross-Site Scripting (XSS) vulnerability in the Canto Testimonials WordPress plugin (version 1.0 and earlier). It occurs because the plugin does not properly sanitize or escape user-supplied input in the 'fx' shortcode attribute. This allows authenticated users with Contributor-level access or higher to inject malicious scripts into testimonial pages. These scripts then execute whenever any user views the affected page. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers with Contributor-level access to inject arbitrary JavaScript into testimonial pages. The injected scripts can execute in the browsers of users who visit those pages, potentially leading to session hijacking, defacement, theft of sensitive information, or other malicious actions. Since the vulnerability requires authenticated access, it poses a risk primarily from insiders or compromised accounts with contributor or higher privileges. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update or remove the Canto Testimonials plugin if it is version 1.0 or below. Restrict Contributor-level and higher user permissions to trusted users only, as the vulnerability requires authenticated access. Additionally, monitor and sanitize any user-supplied shortcode attributes, especially the 'fx' attribute, to prevent stored cross-site scripting. Consider disabling or limiting the use of the 'fx' shortcode attribute until a patched version is available. [1]