Shopping Cart & eCommerce Store <= 5.2.4 - Cross-Site Request Forgery to Settings Update

2022-03-28 00:00
WPScanTeam

Strategic Overview

Status
Patched in 5.2.5
Affected Version
<= 5.2.4
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Shopping Cart & eCommerce Store vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Shopping Cart & eCommerce Store WordPress plugin, affecting versions <= 5.2.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 5.2.5; sites on affected versions should update now. Disclosed March 2022, reported by WPScanTeam.

Vulnerability Overview

The Shopping Cart & eCommerce Store plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.2.4. This is due to missing or incorrect nonce validation on the 'ec_admin_ajax_save_design_settings' AJAX action. This makes it possible for unauthenticated attackers to change arbitrary design settings on the vulnerable service via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site. A successful exploit has high impact on integrity.

CWE-352: Cross-Site Request Forgery (CSRF)

Shopping Cart & eCommerce Store <= 5.2.4 carries this weakness at ec_admin_ajax_save_design_settings, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Shopping Cart & eCommerce Store the fix is 5.2.5: builds <= 5.2.4 are affected, anything from 5.2.5 onward is not.

Remediation

Update to version 5.2.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Shopping Cart & eCommerce Store: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Shopping Cart & eCommerce Store 5.2.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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