CVE-2022-2863 json
WPvivid Backup < 0.9.76 - Admin+ Arbitrary File Read
published 2022-09-16 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-35097
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 25.1%
- EPSS 25.1% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The Migration, Backup, Staging WordPress plugin before 0.9.76 does not sanitise and validate a parameter before using it to read the content of a file, allowing high privilege users to read any file from the web server via a Traversal attack
Patch / fix
- wpvivid migration,_backup,_staging 0.9.76
Exploit prediction
25.10% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template WordPress WPvivid Backup <0.9.76 - Local File Inclusion nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/cb6a3304-2166-47a0-a011-4dcacaa133e5 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2022/Oct/0 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/168616/WordPress-WPvivid-Backup-Path-Traversal.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Unknown Migration, Backup, Staging – WPvivid
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
wpscan.com
/vulnerability/cb6a3304-2166-47a0-a011-4dcacaa133e5
exploit, patch, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Oct/0
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/168616/WordPress-WPvivid-Backup-Path-Traversal.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-2863
- NVD CVE-2022-2863
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.