Unauthorized account connection via forged requests
Published Jul 2, 2026 · Updated Jul 2, 2026
CSRF in pCloud WP Backup 2.0.2 and earlier allows remote attackers to submit forged requests through the pCloud account-connection flow. The vendor identifies that flow as the affected locus but has not published the request handler or omitted validation operation. Exploitation requires an authenticated administrator to interact with attacker-controlled content; the exact account change and exposed data remain undisclosed.
Summary
What happened
CSRF in pCloud WP Backup 2.0.2 and earlier allows remote attackers to submit forged requests through the pCloud account-connection flow. The vendor identifies that flow as the affected locus but has not published the request handler or omitted validation operation. Exploitation requires an authenticated administrator to interact with attacker-controlled content; the exact account change and exposed data remain undisclosed.
The record
- CVE
- CVE-2026-57757
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- pCloud
- Product
- pCloud WP Backup
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=2.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo