wp-db-backup Plugin 2.2.4 on WordPress Access Control Brute Force information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in wp-db-backup Plugin 2.2.4 on WordPress. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component Access Control. The manipulation leads to information disclosure (Brute Force). This vulnerability is uniquely identified as CVE-2014-10076. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in wp-db-backup Plugin 2.2.4 on WordPress (Backup Software) and classified as problematic. This issue affects an unknown function of the component Access Control. The manipulation with an unknown input leads to a information disclosure vulnerability (Brute Force). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
The wp-db-backup plugin 2.2.4 for WordPress relies on a five-character string for access control, which makes it easier for remote attackers to read backup archives via a brute-force attack.
The bug was discovered 11/02/2014. The weakness was disclosed 10/05/2018 (Website). The advisory is shared at vapidlabs.com. The identification of this vulnerability is CVE-2014-10076 since 10/05/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1433 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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
Name: Brute ForceClass: Information disclosure / Brute Force
CWE: CWE-200 / CWE-284 / CWE-266
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/02/2014 🔍10/05/2018 🔍
10/05/2018 🔍
10/05/2018 🔍
10/06/2018 🔍
03/29/2020 🔍
Sources
Advisory: vapidlabs.comStatus: Not defined
CVE: CVE-2014-10076 (🔍)
GCVE (CVE): GCVE-0-2014-10076
GCVE (VulDB): GCVE-100-124817
Entry
Created: 10/06/2018 07:48Updated: 03/29/2020 21:02
Changes: 10/06/2018 07:48 (59), 03/29/2020 21:02 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.