WordPress component: A security weakness
WordPress component is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- WordPress component
- Plugin slug
- Not applicable
- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- May 18, 2017
Update, patch or deactivate.
Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
In WordPress before 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API.
NVD vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Primary and upstream sources
- NVD record for CVE-2017-9065
- Upstream reference debian.org
- Upstream reference securityfocus.com
- Upstream reference securitytracker.com
- WordPress upstream reference codex.wordpress.org
- GitHub upstream reference github.com
- WordPress upstream reference wordpress.org
- Upstream reference wpvulndb.com
- Upstream reference debian.org
- Upstream reference securityfocus.com
- Upstream reference securitytracker.com
- WordPress upstream reference codex.wordpress.org
- GitHub upstream reference github.com
- WordPress upstream reference wordpress.org
- Upstream reference wpvulndb.com