dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-57766

HIGH · 8.8 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 7 weeks old

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 · unedited
Unauthenticated Cross Site Request Forgery (CSRF) in WPIDE – File Manager & Code Editor <= 3.5.6 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 confidence

Unauthenticated Cross Site Request Forgery (CSRF) vulnerability in the WPIDE WordPress plugin (File Manager & Code Editor) affecting versions up to and including 3.5.6. The lack of CSRF protection allows attackers to trick administrators into performing unintended file operations (create, modify, delete files) on the WordPress filesystem through maliciously crafted requests.

MitigationUpdate WPIDE plugin to version 3.5.7 or later which includes CSRF token validation. Until patched, monitor admin actions and consider disabling the plugin if not actively used.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate WPIDE plugin directory
    Check the WordPress plugins folder (wp-content/plugins/) for a folder named 'wpide' or 'WPIDE'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins and look for 'WPIDE' or 'File Manager & Code Editor'.
    Affected if The WPIDE plugin folder exists in the plugins directory or the plugin appears in the WordPress admin plugin list.
  2. Identify installed WPIDE version
    In WordPress admin, go to Plugins > Installed Plugins and find WPIDE. The version number is displayed below the plugin name. Alternatively, open the main plugin file (wp-content/plugins/wpide/wpide.php or similar) and look for the 'Version' header in the plugin comment block.
    Affected if A version number is found in the plugin metadata.
  3. Compare version against vulnerable range
    Compare the installed version to the affected range. Vulnerable versions are up to and including 3.5.6. If your version is 3.5.6 or lower, you are running a vulnerable version. If your version is 3.5.7 or higher, you are not affected.
    Affected if The installed version is 3.5.6 or lower.
  4. Verify plugin activation status
    In WordPress admin under Plugins > Installed Plugins, check if WPIDE shows as 'Active'. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if WPIDE is included.
    Affected if The plugin is currently active in WordPress.

You are affected if WPIDE (File Manager & Code Editor) plugin version 3.5.6 or lower is installed and active in your WordPress environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPIDE plugin to version 3.5.7 or later which includes CSRF token validation. Until patched, monitor admin actions and consider disabling the plugin if not actively used.

Recommended fix Moderate confidence

Latest version available on WordPress.org (version higher than 3.5.6)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WPIDE – File Manager & Code Editor' in the list
  4. If the plugin shows version 3.5.6 or lower, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/wpide and upload it via Plugins > Add New > Upload Plugin
  6. After update, verify the new version number reflects a version higher than 3.5.6

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57766 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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