Security readout for executives and security teams
Plain-English summary
CVE-2016-11005 is a cross-site scripting issue in the WordPress Instalinker plugin before version 1.1.2. A malicious link or request could cause script execution in a user's browser. The public record does not provide CVSS scoring or confirmed exploitation, so urgency depends on whether the plugin is installed and exposed.
Executive priority
Treat as a targeted legacy WordPress cleanup item, not a crisis. Prioritize sites that are internet-facing, handle authenticated users, or still run old third-party plugins.
Technical view
The CVE describes XSS in `includes/instalinker-admin-preview.php` via the `client_id` parameter in Instalinker before 1.1.2. Public details identify the vulnerable endpoint and version range, but the source bundle does not include CVSS, CWE mapping, authentication requirements, or vendor remediation text beyond the pre-1.1.2 affected statement.
Likely exposure
Exposure is limited to WordPress sites running the Instalinker plugin earlier than 1.1.2. The evidence does not confirm whether exploitation requires authentication, administrator interaction, or specific configuration.
Exploitation context
The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The issue is still relevant for legacy WordPress estates because old plugins can remain installed long after support or usage ends.
Researcher notes
The public record is sparse: no CVSS, CWE, detailed prerequisites, or confirmed exploit activity are included. Analysis should avoid assuming impact beyond XSS in the identified Instalinker endpoint and version range.
Mitigation direction
- Inventory WordPress sites for the Instalinker plugin.
- Upgrade Instalinker to 1.1.2 or later where available.
- Remove the plugin if it is unused or unsupported.
- Check vendor/plugin guidance before making production changes.
- Review WordPress plugin update controls for legacy sites.
Validation and detection
- Confirm each WordPress site is not running Instalinker below 1.1.2.
- Review web logs for requests to the named preview PHP file.
- Check whether the vulnerable plugin file is publicly reachable.
- Verify remediation in staging before production rollout.
- Document any sites where plugin version cannot be confirmed.
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.
CVE-2016-11005 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/instalinker/#developersCVE reference · x_refsource_MISC
- https://rastating.github.io/instalinker-reflected-xss-information-disclosure/CVE reference · x_refsource_MISC
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.