CVE-2026-92535: Make Connector <= 1.6.6 - Unauthenticated Sensitive Information Exposure in REST API '/wp/v2/{users,posts,comments,terms}' Endpoints

Published Nov 18, 2026
·
Updated

The Make Connector plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.6 via the includecustomfields. This makes it possible for unauthenticated attackers to extract arbitrary admin-selected user, post, comment, and term metadata exposed via core REST endpoints — including active session tokens with source IP, user-agent, login and expiry timestamps, capability sets, and any other admin-selected private meta keys including protected underscore-prefixed entries. This is exploitable because the plugin's meta picker queries all meta keys from the database without filtering, offering protected underscore-prefixed keys such as sessiontokens and wpcapabilities for administrator selection; if any such keys are selected, their values become readable without any credentials.

Affected Software

1 affected component
Make Make Connector<=1.6.6

Event History

Nov 18, 2026
CVE Published
via MITRE·01:32 PM
Data Sourced
via MITRE·01:32 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed in practice?

Exposure depends on whether an administrator has selected metadata keys through include_custom_fields. Installations that selected protected or private keys, such as session_tokens or wp_capabilities, can expose those values through the affected REST endpoints.

2

Does an attacker need an account or other prior access?

No. The issue is exploitable without credentials through the WordPress core REST endpoints for users, posts, comments, and terms.

3

How can an administrator determine whether sensitive data may be exposed?

Review the metadata keys selected in the plugin's include_custom_fields configuration. Any selected private or protected underscore-prefixed key should be treated as potentially readable through the affected REST endpoints.

4

What types of information could be disclosed if sensitive keys were selected?

The exposed metadata can include active session tokens with source IP addresses, user-agent strings, login and expiry timestamps, capability sets, and other administrator-selected private metadata.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203