Skip to main content
CVE-2026-92535VulnerabilityPublished

The Make Connector plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-92535· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 18 Nov 2026, 16:53 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
integromatMake ConnectorAffected
  • <=1.6.6
Fixed in–

AI-suggested

Users should monitor the vendor's advisory for updates. Until a fix is available, administrators should avoid selecting sensitive meta keys in the plugin's configuration to minimize exposure. Additionally, restricting access to REST endpoints or disabling the plugin temporarily may reduce risk.

Description

The Make Connector plugin for WordPress versions up to and including 1.6.6 suffers from a Sensitive Information Exposure vulnerability. This flaw allows unauthenticated attackers to access arbitrary user, post, comment, and term metadata through core REST endpoints if the admin has selected certain meta keys. Sensitive data exposed can include active session tokens, capability sets, and other private metadata, including protected underscore-prefixed keys. The vulnerability arises because the plugin's meta picker queries all meta keys without filtering, making protected data readable without authentication.

References

Community reviews

Loading reviews…