Extra Charges To Payment Gateway For WooCommerce <= 2.0.2.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting

2021-02-08 00:00
Anonymous

Strategic Overview

Status
Unpatched
Affected Version
<= 2.0.2.1
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all Extra Charges To Payment Gateway For WooCommerce (Standard) vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Extra Charges To Payment Gateway For WooCommerce (Standard) WordPress plugin, affecting versions <= 2.0.2.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed February 2021.

Vulnerability Overview

The Extra Charges To Payment Gateway For WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the add_form_fields() method, hooked to the admin_head action in versions up to, and including, 2.0.2.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthorized (subscriber-level) attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Extra Charges To Payment Gateway For WooCommerce (Standard) <= 2.0.2.1 carries this weakness at add_form_fields(), and reaching it takes an account at Subscriber level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. No fixed build of this plugin is recorded for Extra Charges To Payment Gateway For WooCommerce (Standard) yet, so installs running <= 2.0.2.1 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C