CVE-2026-1060

WP Adminify <= 4.0.7.7 - Unauthenticated Sensitive Information Exposure via 'get-addons-list' REST API

2026-01-27 00:00
ibrahimsql

Strategic Overview

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

At a glance

CVE-2026-1060 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Adminify WordPress plugin, affecting versions <= 4.0.7.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.7.8; sites on affected versions should update now. Disclosed January 2026, reported by ibrahimsql.

Vulnerability Overview

The WP Adminify plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.0.7.7 via the /wp-json/adminify/v1/get-addons-list REST API endpoint. The endpoint is registered with permission_callback set to __return_true, allowing unauthenticated attackers to retrieve the complete list of available addons, their installation status, version numbers, and download URLs.

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 privileges on the target site, and no interaction from a victim user.

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

Reaching this weakness in Adminify <= 4.0.7.7 takes no account at all. 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.0.7.8: builds <= 4.0.7.7 are affected, anything from 4.0.7.8 onward is not.

Remediation

Update to version 4.0.7.8, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Adminify 4.0.7.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1060https://www.wordfence.com/threat-intel/vulnerabilities/id/7ecb4f95-346e-49b3-859f-44f28a72f065https://nvd.nist.gov/vuln/detail/CVE-2026-1060

Related records

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