Security readout for executives and security teams
Plain-English summary
Older WordPress versions could mishandle a specially crafted template name and run unwanted script in the template list view. For organizations still running WordPress before 4.8.2, this creates admin-console risk, but the supplied sources do not show active exploitation or a CVSS score.
Executive priority
Treat this as a patch-compliance issue for legacy WordPress. It is not KEV-listed in the supplied data, but unpatched WordPress admin surfaces create avoidable business risk.
Technical view
CVE-2017-14720 is a WordPress cross-site scripting issue fixed in WordPress 4.8.2. The exposed surface is the template list view, where a crafted template name could trigger script execution. Public details in the bundle are sparse and do not define CWE, CVSS, or exact privileges required.
Likely exposure
Exposure is most likely on WordPress installations older than 4.8.2, including Debian-packaged WordPress before the DSA-3997 update. Current, maintained WordPress deployments should already be patched.
Exploitation context
The source bundle does not provide evidence of active exploitation, and CISA KEV status is false. Exploitation would require a crafted template name reaching the vulnerable template list view; the sources do not fully document prerequisites.
Researcher notes
The record lacks CVSS, CWE, and detailed exploit prerequisites. Anchor assessment to WordPress 4.8.2, Debian DSA-3997, and changeset 41412. Avoid claiming exploitability beyond crafted template-name XSS in the template list view.
Mitigation direction
- Upgrade WordPress to version 4.8.2 or later.
- Apply Debian DSA-3997 packages where WordPress is managed through Debian.
- Review current WordPress vendor guidance for any backport-specific instructions.
- Limit template and theme management access to trusted administrators.
Validation and detection
- Inventory WordPress versions across all public and internal sites.
- Confirm each instance runs WordPress 4.8.2 or a vendor-patched build.
- Check package records for Debian DSA-3997 remediation where applicable.
- Review theme/template inventory for unexpected or untrusted entries.
- Verify admin template list pages render safely after patching.
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-2017-14720 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
- DSA-3997CVE reference · vendor-advisory, x_refsource_DEBIAN
- https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/CVE reference · x_refsource_MISC
- https://core.trac.wordpress.org/changeset/41412CVE 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.