Awesome Testimonials CVE-2025-62933
HIGHSeverity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
No privileges required; user interaction from an admin is the gating factor; scope changes because stored XSS impacts other users.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
Cross-Site Request Forgery (CSRF) vulnerability in Prakash Awesome Testimonials awesome-testimonials allows Stored XSS.This issue affects Awesome Testimonials: from n/a through <= 2.2.1.
AnalysisAI
Stored cross-site scripting via cross-site request forgery in the Awesome Testimonials WordPress plugin up to version 2.2.1 allows unauthenticated attackers to inject malicious scripts that execute in the browsers of site visitors. Exploitation requires a logged-in administrator to be tricked into clicking a crafted link, but no other special configuration is necessary. No active exploitation or public proof-of-concept has been identified at this time.
Technical ContextAI
The vulnerability arises from a missing or improperly implemented anti-CSRF token (nonce) in the plugin’s testimonial submission form, classified as CWE-352 (Cross-Site Request Forgery). When an authenticated administrator is coerced into submitting a malicious request, the plugin processes it and stores attacker-controlled JavaScript without sanitization, enabling stored XSS. The affected product is a WordPress plugin (slug: awesome-testimonials) as recorded in the Patchstack database, and the specific flaw relates to the plugin’s handling of user-supplied content within the WordPress administrative interface.
Affected ProductsAI
Awesome Testimonials plugin for WordPress versions up to and including 2.2.1 are affected. Details are available in the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/awesome-testimonials/vulnerability/wordpress-awesome-testimonials-plugin-2-2-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve.
RemediationAI
Update to Awesome Testimonials version 2.2.2 or later, which contains the vendor-supplied fix (as indicated by Patchstack). If immediate patching is not possible, consider temporarily disabling the plugin until the update can be applied. No compensating control can fully eliminate the CSRF risk without a code fix, but enforcing strict SameSite cookie attributes and training administrators not to click untrusted links while authenticated may reduce exposure.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today