WordPress security changelog
MEDIUM CVE-2023-4637 Modified

WPvivid: A security weakness

WPvivid is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score 5.3 CVSS 3.1 · nvd@nist.gov
Component
WPvivid
Plugin slug
wpvivid-backuprestore
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 05, 2024
Weakness
CWE-862 — Missing Authorization

This CVE was published Feb 05, 2024 and is one of 12 known issues for this plugin.

What to do

Update, patch or deactivate.

Update WPvivid to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The WPvivid plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the restore() and get_restore_progress() function in versions up to, and including, 0.9.94. This makes it possible for unauthenticated attackers to invoke these functions and obtain full file paths if they have access to a back-up ID.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

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

References

Primary and upstream sources