CVE-2025-14378
Stored XSS in Quick Testimonials WordPress Plugin Allows Admin Script Injection
Publication date: 2025-12-13
Last updated on: 2025-12-13
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | quick_testimonials | * |
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?
The Quick Testimonials plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to 2.1. This occurs because the plugin does not properly sanitize input or escape output in the admin settings. As a result, authenticated users with administrator-level permissions or higher can inject malicious web scripts that execute when other users access the affected pages. This vulnerability specifically affects multi-site installations and those where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with administrator-level access to inject malicious scripts into the website. These scripts can execute in the browsers of users who visit the infected pages, potentially leading to theft of sensitive information, session hijacking, or other malicious actions. Since it requires high privileges and affects multi-site or restricted HTML environments, the impact is limited but can compromise the integrity and security of the affected WordPress sites.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that you update the Quick Testimonials plugin to a version later than 2.1 where the issue is fixed. Additionally, review administrator-level permissions to limit access, especially in multi-site installations and where unfiltered_html is disabled. Applying strict input sanitization and output escaping in admin settings can also help reduce risk.