Security readout for executives and security teams
Plain-English summary
CVE-2016-10964 is a cross-site scripting flaw in the WordPress dwnldr plugin before version 1.01. A specially crafted User-Agent value could be stored and later rendered in a browser. Business urgency depends on whether this legacy plugin is installed and whether administrators or privileged users can view the affected data.
Executive priority
Prioritize this where legacy WordPress sites still run dwnldr below 1.01, especially on public-facing sites administered by privileged users. If the plugin is absent, there is no indicated exposure from this CVE.
Technical view
The CVE describes XSS in dwnldr before 1.01 through the HTTP User-Agent header. The public bundle identifies the issue as stored XSS but provides no CVSS score, CWE, CPE, detailed affected-version matrix, or confirmed exploit activity. Treat exposure as plugin-specific and verify against WordPress plugin records and local installations.
Likely exposure
Likely limited to WordPress sites running the dwnldr plugin below version 1.01. The provided CVE metadata does not identify broader products, platforms, or exact deployment conditions.
Exploitation context
No CISA KEV listing or cited source in the bundle confirms active exploitation. The described vector is an HTTP header, but the bundle does not provide safe operational detail on where the value is stored or rendered.
Researcher notes
Evidence is sparse. The CVE record names dwnldr before 1.01 and User-Agent-based XSS, while the disclosure reference labels it stored XSS. No CVSS, CWE, affected CPEs, or active exploitation evidence is included in the supplied bundle.
Mitigation direction
- Inventory WordPress sites for the dwnldr plugin and installed version.
- Upgrade dwnldr to version 1.01 or later if available from the vendor source.
- Remove or disable the plugin if it is unused or cannot be updated.
- Review WordPress administrator access and session protections around affected sites.
- Check vendor guidance before applying compensating controls.
Validation and detection
- Confirm whether dwnldr is installed on each WordPress instance.
- Record the plugin version and flag anything below 1.01.
- Review web logs for unusual User-Agent values without replaying them.
- Check administrator-facing plugin pages for untrusted rendered header content safely.
- Verify remediation by confirming the plugin is updated, removed, or disabled.
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-10964 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/dwnldr/#developersCVE reference · x_refsource_MISC
- https://rastating.github.io/dwnldr-1-0-stored-xss-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.