CVE-2023-40326

Putler Connector for WooCommerce <= 2.12.0 - Missing Authorization via 'send_resync_request'

2023-08-15 00:00
David

Strategic Overview

Status
Patched in 2.13.0
Affected Version
<= 2.12.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-40326
View all Putler – Simple WooCommerce Analytics for your Store vulnerabilities

At a glance

CVE-2023-40326 is a medium-severity Missing Authorization vulnerability in the Putler WordPress plugin, affecting versions <= 2.12.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.13.0; sites on affected versions should update now. Disclosed August 2023, reported by David.

Vulnerability Overview

The Putler Connector for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the send_resync_request() function called via an AJAX action in versions up to, and including, 2.12.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to send a sync request.

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-862: Missing Authorization

Putler <= 2.12.0 carries this weakness at send_resync_request(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Putler the fix is 2.13.0: builds <= 2.12.0 are affected, anything from 2.13.0 onward is not.

Remediation

Update to version 2.13.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Putler 2.13.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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