WebTotem Backups Security & Risk Analysis

wordpress.org/plugins/wt-backups

WebTotem Backups - this plugin provides a set of tools for creating, managing, and restoring backups of your website.

10 active installs v1.0.1 PHP 7.4+ WP 5.2+ Updated Dec 9, 2024
backupclonerestorewt-backupswtotem
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WebTotem Backups Safe to Use in 2026?

Generally Safe

Score 92/100

WebTotem Backups has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "wt-backups" plugin version 1.0.1 exhibits a significant security concern due to its extensive attack surface being entirely unprotected by authentication checks. All 19 identified AJAX handlers lack proper authorization, meaning any user, regardless of their role or logged-in status, could potentially trigger these functions. While the code analysis shows no dangerous functions, raw SQL queries, or unescaped output, and the vulnerability history is clean, the sheer number of unprotected entry points presents a high risk of privilege escalation or unauthorized actions if a vulnerability exists within these handlers. The presence of Guzzle, a bundled library, could also be a concern if it's outdated, though no specific information on its version is provided.

Despite the lack of recorded vulnerabilities and positive indicators like prepared statements and output escaping, the complete absence of capability checks and nonce checks on AJAX handlers is a critical oversight. This makes the plugin highly susceptible to various attacks, including Cross-Site Request Forgery (CSRF) and unauthorized function execution, assuming the handlers perform sensitive operations. The clean vulnerability history might suggest a lack of active exploitation or a very new plugin, but it does not mitigate the immediate risks posed by the unprotected attack surface.

In conclusion, while "wt-backups" v1.0.1 demonstrates good practices in areas like SQL and output handling, its fundamental flaw lies in the complete lack of security for its AJAX endpoints. This drastically elevates the risk profile, overshadowing the positive aspects. Immediate remediation by implementing proper authentication and authorization for all AJAX handlers is strongly recommended.

Key Concerns

  • 19 AJAX handlers without auth checks
  • No nonce checks on AJAX handlers
  • No capability checks on AJAX handlers
  • Bundled Guzzle library (potential outdatedness)
Vulnerabilities
None known

WebTotem Backups Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

WebTotem Backups Release Timeline

v1.0.1Current
v1.0.0
Code Analysis
Analyzed Apr 16, 2026

WebTotem Backups Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
1
328 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
1

Bundled Libraries

Guzzle

Output Escaping

100% escaped329 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

1 flows
<add_storage> (includes/templates/add_storage.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
19 unprotected

WebTotem Backups Attack Surface

Entry Points19
Unprotected19

AJAX Handlers 19

authwp_ajax_wt_backups_open_popupentry/Common.php:325
authwp_ajax_wt_backups_restore_pageentry/Common.php:326
authwp_ajax_wt_backups_delete_backupentry/Common.php:327
authwp_ajax_wt_backups_progress_checkerentry/Common.php:328
authwp_ajax_wt_backups_next_pageentry/Common.php:329
authwp_ajax_wt_backups_backup_checkingentry/Common.php:330
authwp_ajax_wt_backups_backupentry/Common.php:331
authwp_ajax_wt_backups_restore_checkingentry/Common.php:332
authwp_ajax_wt_backups_restoreentry/Common.php:333
authwp_ajax_wt_backups_activationentry/Common.php:335
authwp_ajax_wt_backups_check_folder_pathentry/Common.php:336
authwp_ajax_wt_backups_save_backup_settingsentry/Common.php:337
authwp_ajax_wt_backups_check_backup_settingsentry/Common.php:338
authwp_ajax_wt_backups_save_storageentry/Common.php:339
authwp_ajax_wt_backups_check_ftpentry/Common.php:340
authwp_ajax_wt_backups_remove_storageentry/Common.php:341
authwp_ajax_wt_backups_upload_backupentry/Common.php:342
authwp_ajax_wt_backups_add_cloud_storageentry/Common.php:343
authwp_ajax_wt_backups_check_zip_existentry/Common.php:344
WordPress Hooks 14
filterwp_kses_allowed_htmlentry/Common.php:68
actionadmin_enqueue_scriptsentry/Common.php:288
actioninitentry/Common.php:322
filtercron_schedulesentry/Common.php:351
actionwpentry/Common.php:392
actionwt_backups_init_cronentry/Common.php:404
actionwpentry/Common.php:408
actionwt_backups_init_cron_incrementalentry/Common.php:422
filtercron_schedulesentry/Common.php:427
actionwpentry/Common.php:436
actionwt_backups_five_min_evententry/Common.php:442
actionwpentry/Common.php:445
actionadmin_menuentry/Common.php:516
actionplugins_loadedwt-backups.php:86

Scheduled Events 4

wt_backups_init_cron
wt_backups_init_cron_incremental
wt_backups_five_min_event
wt_backups_hourly_event
Maintenance & Trust

WebTotem Backups Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedDec 9, 2024
PHP min version7.4
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WebTotem Backups Developer Profile

WebTotem

2 plugins · 910 total installs

91
trust score
Avg Security Score
96/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect WebTotem Backups

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/wt-backups/
Version Parameters
wt-backups/style.css?ver=

HTML / DOM Fingerprints

HTML Comments
Protected By WebTotem! Dependencies are not metProtected By WebTotem! ABSPATH constant is not available
FAQ

Frequently Asked Questions about WebTotem Backups