wp-database-backup Plugin up to 4.3.0 on WordPress cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in wp-database-backup Plugin up to 4.3.0 on WordPress. Affected by this issue is some unknown functionality. The manipulation results in cross-site request forgery. This vulnerability is known as CVE-2016-10876. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in wp-database-backup Plugin up to 4.3.0 on WordPress (Backup Software). Affected is an unknown part. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
The wp-database-backup plugin before 4.3.1 for WordPress has CSRF.
The weakness was published 08/12/2019. This vulnerability is traded as CVE-2016-10876 since 08/12/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
Upgrading to version 4.3.1 eliminates this vulnerability.
Similar entries are available at VDB-139799, VDB-139798 and VDB-139797. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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 request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: wp-database-backup Plugin 4.3.1
Timeline
08/12/2019 🔍08/12/2019 🔍
08/13/2019 🔍
11/23/2023 🔍
Sources
Advisory: wordpress.orgStatus: Not defined
CVE: CVE-2016-10876 (🔍)
GCVE (CVE): GCVE-0-2016-10876
GCVE (VulDB): GCVE-100-139800
See also: 🔍
Entry
Created: 08/13/2019 07:11Updated: 11/23/2023 09:20
Changes: 08/13/2019 07:11 (37), 07/25/2020 09:31 (18), 11/23/2023 09:20 (4)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.