Make, formerly Integromat Connector <= 1.5.2 - Authenticated (Subscriber+) Information Disclosure

2022-09-26 00:00
Anonymous

Strategic Overview

Status
Patched in 1.5.3
Affected Plugin
Make Connector
Affected Version
<= 1.5.2
CVSS
6.5Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE pending
View all Make Connector vulnerabilities

At a glance

This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Make Connector WordPress plugin, affecting versions <= 1.5.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.5.3; sites on affected versions should update now. Disclosed September 2022.

Vulnerability Overview

The Make plugin for WordPress is vulnerable to authorization bypass due to a missing capability check and nonce verification on an admin_menu action in versions up to, and including, 1.5.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to download the plugin's logs which may contain sensitive information.

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. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Make Connector <= 1.5.2 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Make Connector the fix is 1.5.3: builds <= 1.5.2 are affected, anything from 1.5.3 onward is not.

Remediation

Update to version 1.5.3, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Make Connector 1.5.3 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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