Security readout for executives and security teams
Plain-English summary
CVE-2026-1060 exposes WP Adminify addon information to anyone on the internet. It does not let an attacker directly change the site, but it can reveal installed addon status, versions, and download URLs that help attackers plan follow-on targeting.
Executive priority
Treat as routine but timely remediation. This is not described as site takeover, but it leaks useful internal plugin details from public websites. Prioritize externally facing WordPress sites and environments with strict information-disclosure requirements.
Technical view
WP Adminify for WordPress is vulnerable through version 4.0.7.7. A REST API endpoint for addon listing was registered with an always-true permission callback, allowing unauthenticated access to addon metadata. CVSS is 5.3, network exploitable, low complexity, no privileges or user interaction required, confidentiality impact low.
Likely exposure
Public WordPress sites running WP Adminify versions up to and including 4.0.7.7 are the likely exposure. Sites with the plugin disabled or absent are not exposed through this plugin endpoint.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The issue is easy to reach remotely without authentication, but the documented impact is information disclosure, mainly useful for reconnaissance.
Researcher notes
Primary evidence is Wordfence, CVE data, and WordPress plugin Trac references. The bundle names versions through 4.0.7.7 as vulnerable and points to a code changeset, but does not provide a clear fixed version statement. Avoid assuming exploitation beyond disclosed metadata access.
Mitigation direction
- Inventory WordPress sites for WP Adminify installations.
- Update WP Adminify to a fixed or latest vendor-provided version when available.
- If no update is available, consider disabling the plugin until vendor guidance is available.
- Remove WP Adminify from sites where it is not required.
- Monitor web logs for unusual access to the Adminify REST addon endpoint.
Validation and detection
- Confirm whether WP Adminify is installed on each WordPress site.
- Check installed WP Adminify versions against the vulnerable range through 4.0.7.7.
- After updating, verify unauthenticated users cannot retrieve addon metadata.
- Review WordPress plugin update history for the referenced changeset or later vendor release.
- Document any internet-facing affected sites for remediation tracking.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1060 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7ecb4f95-346e-49b3-859f-44f28a72f065?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/adminify/tags/4.0.6.1/Libs/Addons.php#L54CVE reference
- https://plugins.trac.wordpress.org/changeset/3442928/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.