WPIDE · CVE-2026-124251 · Package
FIX → 3.6.5
WPIDE – File Manager & Code Editor, a WordPress plugin, has a cross-site request forgery flaw in versions through 3.6.4. An attacker can trick a logged-in user's browser into sending requests to the plugin that the user did not intend.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the WPIDE – File Manager & Code Editor WordPress plugin at version 3.6.4 or earlier are in the affected range. The flaw needs a logged-in administrator to visit a malicious page, so sites that do not run the plugin can skip it. The sources do not say which actions the forged requests can reach.
Not affected if no-logged-in-admin-browsing, plugin-not-installed
Who cares self-hosted, wordpress, wpide
wp plugin get wpide --field=version or look under Plugins in WordPress admin; 3.6.4 or lower is in the affected range.wp plugin update wpide) and confirm the version afterwards.Upgrade to 3.6.5
Update WPIDE to 3.6.5 (current release on wordpress.org; first version above the affected range <=)
Cross-Site Request Forgery (CSRF) vulnerability in XplodedThemes WPIDE – File Manager & Code Editor wpide allows Cross Site Request Forgery.This issue affects WPIDE – File Manager & Code Editor: from n/a through 3.6.4.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
3.6.4