| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in WordPress up to 4.4.10/4.5.9/4.6.6/4.7.5/4.8.1. This issue affects some unknown processing of the component oEmbed Discovery. The manipulation leads to cross site scripting. This vulnerability is referenced as CVE-2017-14724. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in WordPress up to 4.4.10/4.5.9/4.6.6/4.7.5/4.8.1 (Content Management System). It has been rated as problematic. This issue affects an unknown functionality of the component oEmbed Discovery. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
Before version 4.8.2, WordPress was vulnerable to cross-site scripting in oEmbed discovery.
The bug was discovered 09/19/2017. The weakness was published 09/23/2017 by Security Team (Alex) with WordPress Security Team (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2017-14724 since 09/23/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 103793 (Debian DSA-3997-1 : wordpress - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176177 (Debian Security Update for wordpress (DSA 3997-1)).
Upgrading to version 4.4.11, 4.5.10, 4.6.7, 4.7.6 or 4.8.2 eliminates this vulnerability. The upgrade is hosted for download at core.trac.wordpress.org. A possible mitigation has been published 3 weeks after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (103793), SecurityFocus (BID 100912†) and SecurityTracker (ID 1039553†). Similar entries are available at VDB-107039, VDB-107040, VDB-107041 and VDB-107042. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 4.4
- 4.4 Beta1
- 4.4 Beta2
- 4.4 Beta3
- 4.4 Beta4
- 4.4 rc1
- 4.4.0
- 4.4.1
- 4.4.2
- 4.4.3
- 4.4.4
- 4.4.5
- 4.4.6
- 4.4.7
- 4.4.8
- 4.4.9
- 4.4.10
- 4.5
- 4.5 Beta1
- 4.5 Beta2
- 4.5 Beta3
- 4.5 Beta4
- 4.5 rc1
- 4.5 rc2
- 4.5 rc3
- 4.5.1
- 4.5.1 rc1
- 4.5.1 rc2
- 4.5.2
- 4.5.3
- 4.5.4
- 4.5.5
- 4.5.6
- 4.5.7
- 4.5.8
- 4.5.9
- 4.6
- 4.6 Beta1
- 4.6 Beta2
- 4.6 Beta3
- 4.6 Beta4
- 4.6 rc1
- 4.6 rc2
- 4.6 rc3
- 4.6 rc4
- 4.6.1
- 4.6.1 rc1
- 4.6.2
- 4.6.3
- 4.6.4
- 4.6.5
- 4.6.6
- 4.7
- 4.7 Beta1
- 4.7 Beta2
- 4.7 Beta3
- 4.7 Beta4
- 4.7 rc1
- 4.7 rc2
- 4.7 rc3
- 4.7.1
- 4.7.1 rc1
- 4.7.2
- 4.7.3
- 4.7.3 rc1
- 4.7.4
- 4.7.4 rc1
- 4.7.5
- 4.8
- 4.8 Beta1
- 4.8 Beta2
- 4.8 rc1
- 4.8 rc2
- 4.8.1
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 103793
Nessus Name: Debian DSA-3997-1 : wordpress - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 53378
OpenVAS Name: Debian Security Advisory DSA 3997-1 (wordpress - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: WordPress 4.4.11/4.5.10/4.6.7/4.7.6/4.8.2
Timeline
09/19/2017 🔍09/19/2017 🔍
09/23/2017 🔍
09/23/2017 🔍
09/23/2017 🔍
09/24/2017 🔍
10/10/2017 🔍
10/11/2017 🔍
10/12/2017 🔍
01/14/2021 🔍
Sources
Product: wordpress.comAdvisory: 41448⛔
Researcher: Security Team (Alex)
Organization: WordPress Security Team
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-14724 (🔍)
GCVE (CVE): GCVE-0-2017-14724
GCVE (VulDB): GCVE-100-107045
OVAL: 🔍
SecurityFocus: 100912 - WordPress Prior to 4.8.2 Multiple Input Validation Security Vulnerabilities
SecurityTracker: 1039553
See also: 🔍
Entry
Created: 09/24/2017 09:45Updated: 01/14/2021 08:45
Changes: 09/24/2017 09:45 (86), 06/07/2020 20:33 (4), 01/14/2021 08:45 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.