CVE-2026-57757
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Cross Site Request Forgery (CSRF) in pCloud WP Backup <= 2.0.2 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnauthenticated Cross Site Request Forgery (CSRF) vulnerability in pCloud WP Backup plugin versions 2.0.2 and earlier allows remote attackers to trick authenticated administrators into executing unintended actions via crafted HTTP requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if pCloud WP Backup plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'pcloud-wp-backup', 'pcloud-backup', or similar pCloud-related folder. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';Affected if The pCloud WP Backup plugin folder exists in the plugins directory or appears in active_plugins list
-
Determine the installed plugin versionCheck the plugin's main PHP file header for the 'Version' field. Common paths: wp-content/plugins/pcloud-wp-backup/pcloud-wp-backup.php or wp-content/plugins/pcloud-backup/pcloud-backup.php. You can also query: SELECT * FROM wp_postmeta WHERE meta_key = 'version' AND post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'plugin');Affected if The version returned is 2.0.2 or any version lower than 2.0.2
-
Verify the plugin is activeQuery the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%pcloud%'; or check if the plugin appears in the WordPress admin Plugins page.Affected if The plugin is active and enabled in WordPress (required for the CSRF to target authenticated administrators)
-
Confirm the plugin handles state-changing actions without noncesReview the plugin's PHP source code for form submissions and AJAX actions. Search for functions that modify settings, create backups, or perform administrative tasks. Check if wp_nonce_field(), wp_verify_nonce(), or check_admin_referer() are used. grep -r 'wp_nonce' wp-content/plugins/pcloud* 2>/dev/nullAffected if The plugin performs administrative actions (plugin settings, backup creation, restore, etc.) without verifying a nonce token
You are affected if pCloud WP Backup plugin version 2.0.2 or earlier is installed, active, and handles administrative actions without CSRF nonce verification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade pCloud WP Backup to the latest version; implement anti-CSRF tokens (nonces) on all state-changing plugin actions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57757 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data