GHSA-PHQ4-GGCM-GJ84
Vulnerability from github – Published: 2026-07-23 12:32 – Updated: 2026-07-23 12:32The GutenKit Blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/gutenkit/v1/mailchimp/get/lists and /wp-json/gutenkit/v1/mailchimp/get/interests REST API endpoints in versions up to, and including, 2.4.12. Both endpoints are registered with permission_callback => '__return_true', and their callbacks read the site's stored Mailchimp API key from the gutenkit_settings_list option and proxy Mailchimp audience/list, merge-field, interest-category, interest-name, and subscriber-count metadata back to the caller with no login, nonce, or capability check. This makes it possible for unauthenticated attackers to retrieve private Mailchimp audience configuration information from any site that has configured the GutenKit Mailchimp integration.
{
"affected": [],
"aliases": [
"CVE-2026-15827"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-23T10:16:51Z",
"severity": "MODERATE"
},
"details": "The GutenKit Blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/gutenkit/v1/mailchimp/get/lists and /wp-json/gutenkit/v1/mailchimp/get/interests REST API endpoints in versions up to, and including, 2.4.12. Both endpoints are registered with permission_callback =\u003e \u0027__return_true\u0027, and their callbacks read the site\u0027s stored Mailchimp API key from the gutenkit_settings_list option and proxy Mailchimp audience/list, merge-field, interest-category, interest-name, and subscriber-count metadata back to the caller with no login, nonce, or capability check. This makes it possible for unauthenticated attackers to retrieve private Mailchimp audience configuration information from any site that has configured the GutenKit Mailchimp integration.",
"id": "GHSA-phq4-ggcm-gj84",
"modified": "2026-07-23T12:32:22Z",
"published": "2026-07-23T12:32:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-15827"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.11/includes/Routes/MailChimp.php#L141"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.11/includes/Routes/MailChimp.php#L17"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.11/includes/Routes/MailChimp.php#L43"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.11/includes/Routes/MailChimp.php#L62"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.6/includes/Routes/MailChimp.php#L141"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.6/includes/Routes/MailChimp.php#L17"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.6/includes/Routes/MailChimp.php#L43"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/gutenkit-blocks-addon/tags/2.4.6/includes/Routes/MailChimp.php#L62"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?reponame=\u0026old=3618270%40gutenkit-blocks-addon\u0026new=3618270%40gutenkit-blocks-addon"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/7430594c-3a71-4b24-875b-014e03be868f?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.