CVE-2020-36835

Migration, Backup, Staging – WPvivid <= 0.9.35 - Sensitive Information Disclosure

2020-03-23 00:00

Strategic Overview

Status: Patched in 0.9.36
Affected Plugin: WPvivid — Backup, Migration & Staging
Affected Version: < 0.9.36
CVSS: 4.9Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2020-36835

View all WPvivid — Backup, Migration & Staging vulnerabilities

At a glance

CVE-2020-36835 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPvivid WordPress plugin, affecting versions < 0.9.36. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). The issue is fixed in version 0.9.36; sites on affected versions should update now. Disclosed March 2020, reported by WebARX Security.

Vulnerability Overview

The Migration, Backup, Staging – WPvivid plugin for WordPress is vulnerable to sensitive information disclosure of a WordPress site's database due to missing capability checks on the wp_ajax_wpvivid_add_remote AJAX action that allows low-level authenticated attackers to send back-ups to a remote location of their choice for review. This affects versions up to, and including 0.9.35.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in WPvivid < 0.9.36 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WPvivid the fix is 0.9.36: builds < 0.9.36 are affected, anything from 0.9.36 onward is not.

Remediation

Update to version 0.9.36, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WPvivid 0.9.36 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-36835 https://www.wordfence.com/threat-intel/vulnerabilities/id/90c3f8bc-fc41-4ba7-b9f2-8873203d5794 https://nvd.nist.gov/vuln/detail/CVE-2020-36835

Related records

Same weakness class

Other vulnerabilities in WPvivid — Backup, Migration & Staging

CVSS Vector

4.9

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/