CVE-2024-11814 MEDIUM

CVE-2024-11814: Additional Custom Order Status for WooCommerce <= 1.6.0 - Reflected Cross-Site Scripting

Vendor Wpcodefactory
Product Additional Custom Order Status for WooCommerce
Weakness CWE-79 · XSS
Published December 4, 2024
Last update April 8, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Additional Custom Order Status for WooCommerce plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the wfwp_wcos_delete_finished, wfwp_wcos_delete_fallback_finished, wfwp_wcos_delete_fallback_orders_updated, and wfwp_wcos_delete_fallback_status parameters in all versions up to, and including, 1.6.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

The Additional Custom Order Status for WooCommerce plugin contains a stored cross-site scripting (XSS) vulnerability in versions up to 1.6.0. An attacker can inject malicious scripts into custom order status fields that execute when site administrators or other users view the affected pages. The vulnerability requires user interaction to trigger but can affect multiple users across the site.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in the browsers of site admins and other users viewing order statuses.

Potential impact on your site

04Site Impact

Attackers can steal admin session cookies, modify site content, or redirect users to malicious sites.

Conditions required to exploit

05Prerequisites

No authentication required, but the victim must visit a page containing the injected payload.

Key dates

06Disclosure timeline

December 4, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE