Skip to content
Laskyr

Plugins · pcloud-wp-backup · data as of 2026-11-04

Is pCloud WP Backup safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.0.11)

As of 2026-11-04. 2 issues are on record for older versions; version 2.0.4 or newer fixes all of them that state a fix.

Latest version
2.0.11
Last updated
2026-09-23
Active installs
1,000+
Known issues on record
2
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 8.0+

The pCloud WP Backup plugin will help you backup everything on your blog with one click and store it in the cloud in the most secure way. — by ploudapp

What to do

  1. Update to the latest version (2.0.11). Anything older than 2.0.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get pcloud-wp-backup --field=version shows what you run; wp plugin update pcloud-wp-backup updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.5 CVE-2026-14503 · published 2026-07-17

Information disclosure in pCloud WP Backup (2.0.3 and older)

Affected
2.0.3 and older
Fixed in
2.0.4 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The pCloud WP Backup plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.0.3 via the wp2pcl_ajax_process_request_inner. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract force generation of a full-site backup archive written to a publicly accessible directory, exposing wp-config.php database credentials, WordPress secret salts, and the complete PHP source tree. The resulting archive is deposited in the plugin's unprotected tmp/ directory at a predictable URL, making the extracted data accessible to unauthenticated visitors once the backup is triggered.

NVD CVE-2026-14503Wordfence advisoryCode change (fix)Plugin source

high 7.1 CVE-2026-57757 · published 2026-07-02

Cross-site request forgery (CSRF) in pCloud WP Backup (2.0.2 and older)

Affected
2.0.2 and older
Fixed in
2.0.3 *
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Unauthenticated Cross Site Request Forgery (CSRF) in pCloud WP Backup <= 2.0.2 versions.

NVD CVE-2026-57757Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
pCloud WP Backup vulnerability status badge
<a href="https://laskyr.com/plugins/pcloud-wp-backup"><img src="https://laskyr.com/plugins/pcloud-wp-backup/badge.svg" alt="pCloud WP Backup vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit