# CVE-2026-14503: Missing authorization in pCloud WP Backup

> Authenticated subscribers can trigger backups exposing sensitive credentials and source code via predictable public URLs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-6qxr-g8rc-cpg3

## What is CVE-2026-14503?

CVE-2026-14503 is a medium-severity missing authorization vulnerability in ploudapp pCloud WP Backup, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-14503?


## How do I fix CVE-2026-14503?

No fix has been published for CVE-2026-14503 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14503 being exploited?

There is no known exploitation of CVE-2026-14503 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14503 and fix it if it is affected.

What it is: CVE-2026-14503 is a medium-severity missing authorization vulnerability in ploudapp pCloud WP Backup, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14503 in the wild and no public exploit code.

Affected product: ploudapp pCloud WP Backup. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14503/ (Markdown: https://insights.sbomify.com/CVE-2026-14503/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14503
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14503
- OSV: https://osv.dev/vulnerability/CVE-2026-14503

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14503/
Summaries are generated and may contain mistakes; the official description above is the record.