Security readout for executives and security teams
Plain-English summary
CVE-2016-10986 is a cross-site scripting issue in the WordPress Tweet Wheel plugin before 1.0.3.3. Affected sites could expose administrators or visitors to malicious script execution if vulnerable plugin settings are abused. The sources do not provide CVSS scoring or evidence of active exploitation.
Executive priority
Treat this as a targeted legacy WordPress plugin hygiene issue. Prioritize confirmation and remediation if the plugin exists on externally reachable or business-critical sites.
Technical view
The vulnerability is XSS in Tweet Wheel versions before 1.0.3.3 through the consumer_key, consumer_secret, access_token, and access_token_secret fields. Public source data does not include CWE, CVSS, authentication requirements, or a confirmed exploitation chain, so operational risk depends on plugin presence and who can modify those values.
Likely exposure
Exposure appears limited to WordPress installations running the Tweet Wheel plugin before version 1.0.3.3. Organizations without this plugin are not exposed based on the provided sources.
Exploitation context
The CVE is not listed as KEV, and the provided bundle does not cite active exploitation. Public references include a vulnerability database entry, the WordPress plugin developer page, and an original disclosure blog.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, exploit telemetry, or detailed fix notes are included in the provided bundle. Analysis should stay scoped to Tweet Wheel before 1.0.3.3 and the named fields.
Mitigation direction
- Inventory WordPress sites for the Tweet Wheel plugin.
- Upgrade Tweet Wheel to version 1.0.3.3 or later if available.
- Remove or disable the plugin if it is unused or unsupported.
- Restrict WordPress plugin administration to trusted accounts only.
- Check vendor and WordPress guidance for current plugin status.
Validation and detection
- Confirm installed Tweet Wheel versions across all WordPress environments.
- Flag any installation older than version 1.0.3.3.
- Review plugin configuration fields for unexpected markup or scripts.
- Review WordPress administrator activity around plugin configuration changes.
- Confirm vulnerable instances were upgraded, disabled, or removed.
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.
CVE-2016-10986 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://wpvulndb.com/vulnerabilities/8464CVE reference · x_refsource_MISC
- https://wordpress.org/plugins/tweet-wheel/#developersCVE reference · x_refsource_MISC
- https://0x62626262.wordpress.com/2016/04/21/tweet-wheel-xss-vulnerability/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.