mediumCVE-2026-14503

pCloud WP Backup <= 2.0.3 - Missing Authorization on the 'start_backup' AJAX Method to Authenticated (Subscriber+) Arbitrary File Read

Q: What is affected by CVE-2026-14503?

pCloud WP Backup versions listed as affected should be reviewed: up to and including 2.0.3.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

Browse WordPress security risks

ProductpCloud WP Backup

CVSS6.5

EPSS0.00287

UpdatedJuly 19, 2026

Quick answer

pCloud WP Backup should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

up to and including 2.0.3

Fixed versions

2.0.4

How to fix it

pCloud WP Backup is affected by CVE-2026-14503, a missing authorization flaw that can create a public full-site backup. A subscriber can trigger a predictable backup archive that exposes wp-config.php, database credentials, salts, and source code. Update pCloud WP Backup to 2.0.4 or a newer vendor-supported patched release. Prioritize exposed production systems and accounts that can reach the affected feature.

Inventory every pCloud WP Backup deployment, version, exposed endpoint, environment, and owner.
Confirm the installed release is not an affected version up to and including 2.0.3.
Update pCloud WP Backup to 2.0.4 or a newer vendor-supported patched release.
Until the update is complete, deactivate pCloud WP Backup, block start_backup, and deny web access to the plugin tmp directory.
Review relevant logs and find generated archives, subscriber backup requests, public archive downloads, and access to the plugin tmp path.
Purge public archives and rotate WordPress database credentials, salts, API keys, and other secrets stored in the exposed backup.
Clear WordPress, object, page, CDN, and browser caches, then update the asset inventory and close any temporary controls only after validation.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm pCloud WP Backup is on the patched version or mitigation stated above and record the exact deployed version.
Confirm a subscriber cannot start a backup and the plugin temporary directory cannot be downloaded over the web.
Confirm the affected WordPress REST, AJAX, form, shortcode, upload, export, or admin feature is available only to the roles and requests that need it.
Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-14503.

Related categories

WordPress PHP Authorization Bypass Information Disclosure Arbitrary File Write

Related security risks

More published guidance from the same primary category.

high

pCloud WP Backup <= 2.0.4 - Cross-Site Request Forgery

Updated July 13, 2026

medium

Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter

Updated July 24, 2026

high

CVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability

Updated July 24, 2026

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-14503?

pCloud WP Backup versions listed as affected should be reviewed: up to and including 2.0.3.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.