Security readout for executives and security teams
Plain-English summary
WordPress versions before 4.8.2 had a cross-site scripting flaw in oEmbed discovery. In business terms, a vulnerable site could expose users or administrators to malicious script execution in the browser if the flaw is triggered. The source bundle does not provide CVSS, detailed prerequisites, or evidence of active exploitation.
Executive priority
Handle as a legacy hygiene issue unless a vulnerable internet-facing WordPress instance is still present. The fix is old, well identified, and should already be included in supported WordPress versions.
Technical view
CVE-2017-14724 is a WordPress core XSS issue in oEmbed discovery fixed in WordPress 4.8.2. The public bundle cites WordPress, Debian, WPVulnDB, and a core changeset, but does not include CWE, CVSS, exploit maturity, or detailed attack conditions.
Likely exposure
Exposure is likely limited to WordPress installations running versions before 4.8.2, including distribution-packaged WordPress where security updates were not applied.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat exploitation status as unconfirmed, not actively exploited.
Researcher notes
The affected product metadata in the bundle is generic, but the title, description, WordPress release, Debian advisory, and core changeset consistently identify WordPress before 4.8.2. Severity scoring and exploitation prerequisites are not provided.
Mitigation direction
- Upgrade WordPress core to version 4.8.2 or later.
- Apply Debian DSA-3997 updates if using Debian-packaged WordPress.
- Check current WordPress vendor guidance for any later supported update path.
- Prioritize externally reachable and administrator-used WordPress sites first.
Validation and detection
- Inventory WordPress installations and confirm each core version is 4.8.2 or later.
- For Debian systems, verify the WordPress package includes DSA-3997 security updates.
- Confirm affected sites no longer run unsupported pre-4.8.2 WordPress core.
- Review change management records for the September 2017 WordPress security update.
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-14724 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://wpvulndb.com/vulnerabilities/8913CVE reference · x_refsource_MISC
- https://core.trac.wordpress.org/changeset/41448CVE reference · x_refsource_MISC
- https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/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.