CVE-2026-11781

Adminify <= 4.2.9 - Authenticated (Contributor+) Information Exposure

2026-06-11 00:00
Vaibhav Narkhede

Strategic Overview

Status
Patched in 4.2.10
Affected Plugin
Adminify – White Label, Admin Menu Editor, Login Customizer
Affected Version
<= 4.2.9
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-11781
View all Adminify – White Label, Admin Menu Editor, Login Customizer vulnerabilities

At a glance

CVE-2026-11781 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Adminify WordPress plugin, affecting versions <= 4.2.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.2.10; sites on affected versions should update now. Disclosed June 2026, reported by Vaibhav Narkhede.

Vulnerability Overview

The Adminify plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.2.9. This is due to missing capability checks before returning posts, comments, users, and plugin data in the global admin search AJAX handler, allowing any role with edit_posts to retrieve content they should not be able to read. This makes it possible for authenticated attackers, with contributor-level access and above, to access other authors' unpublished post titles, unapproved comment content, user login names, and the site's plugin inventory via the global admin search.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Adminify <= 4.2.9 takes an account at Contributor 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 Adminify the fix is 4.2.10: builds <= 4.2.9 are affected, anything from 4.2.10 onward is not.

Remediation

Update to version 4.2.10, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Adminify 4.2.10 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-11781https://www.wordfence.com/threat-intel/vulnerabilities/id/a2b6ecc1-8957-49b4-941a-a327ae21dd05https://nvd.nist.gov/vuln/detail/CVE-2026-11781

Related records

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