CVE-2026-1060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Adminify WordPress plugin registers a REST API endpoint at /wp-json/adminify/v1/get-addons-list with permission_callback set to __return_true, which unconditionally allows all requests including unauthenticated ones. This exposes sensitive addon metadata including installation status, version numbers, and download URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Adminify plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the file /wp-content/plugins/adminify/plugin.php and look for the Plugin Name header commentAffected if The WP Adminify plugin appears in the list of installed plugins
-
Check the installed version numberIn WordPress admin, click on the WP Adminify plugin to view its details and note the version number, or read the 'Version:' field from the plugin header comment in /wp-content/plugins/adminify/plugin.phpAffected if The version number is lower than 4.0.8 (e.g., 4.0.7, 4.0.6, earlier versions)
-
Test unauthenticated access to the vulnerable endpointSend a GET request to https://yourdomain.com/wp-json/adminify/v1/get-addons-list using curl or a browser (not logged in)Affected if The endpoint returns a 200 OK response with JSON data instead of requiring authentication
-
Verify sensitive addon metadata is exposedExamine the JSON response from the endpoint - look for fields such as addon name, version, download_url, and installation statusAffected if The response contains sensitive information including version numbers, download URLs, or installation status of paid/free addons
You are affected if WP Adminify plugin is installed with a version below 4.0.8 AND the /wp-json/adminify/v1/get-addons-list endpoint returns data without requiring authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to version 4.0.8 or later which should include proper authentication checks. Alternatively, implement a proper permission_callback function (e.g., current_user_can('manage_options')) to restrict endpoint access to authenticated administrators.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data