The WP Database Backup plugin for WordPress is vulnerable to OS Command Injection in versions before 5.2 via the mysqldump function. This vulnerability allows unauthenticated attackers to execute arbitrary commands on the host operating system.
Vendor
wpseeds vulnerabilities
9 published CVES affecting wpseeds, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 1
- High
- 3
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest wpseeds CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 22.1% Framework module
-
MediumCVSS 4.8 EPSS 0.59%
The WP User plugin for WordPress is vulnerable to Stored Cross-Site Scripting via its settings parameters in versions up to, and including, 7.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level...
-
MediumCVSS 4.8 EPSS 0.52%
The WP Database Backup WordPress plugin before 5.9 does not escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks when the unfiltered_html capability is disallowed (for example in multisite setup)
-
HighCVSS 7.5 EPSS 2.4%
The WP Database Backup plugin through 5.5 for WordPress stores downloads by default locally in the directory wp-content/uploads/db-backup/. This might allow attackers to read ZIP archives by guessing random ID numbers, guessing date strings with a 2020_{0..1}{0..2}_{0..3}{0..9} f...
-
MediumCVSS 6.1 EPSS 0.95%
The wp-database-backup plugin before 5.1.2 for WordPress has XSS.
-
MediumCVSS 6.1 EPSS 0.92%
The wp-database-backup plugin before 4.3.3 for WordPress has XSS.
-
HighCVSS 8.8 EPSS 0.68%
The wp-database-backup plugin before 4.3.3 for WordPress has CSRF.
-
MediumCVSS 6.1 EPSS 0.92%
The wp-database-backup plugin before 4.3.1 for WordPress has XSS.
-
HighCVSS 8.8 EPSS 0.69%
The wp-database-backup plugin before 4.3.1 for WordPress has CSRF.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.