WordPress WPIDE – File Manager & Code Editor plugin <= 3.6.4 - Cross Site Request Forgery (CSRF) vulnerability
WPIDE – File Manager & Code Editor plugin versions up to and including 3.6.4 are affected. Fixed in 3.6.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.6.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. WPIDE – File Manager & Code Editor plugin version 3.6.4 and earlier (<= 3.6.4)
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The WPIDE – File Manager & Code Editor plugin for WordPress has a cross-site request forgery flaw. An attacker can trick a logged-in user into clicking a malicious link or visiting a malicious page, which causes the plugin to carry out actions the user did not intend, and the attack can be launched remotely over the network without logging in.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
WPIDE – File Manager & Code Editor plugin version 3.6.4 and earlier (<= 3.6.4)Upgrade to a fixed version: 3.6.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124251 (WordPress WPIDE – File Manager & Code Editor plugin <= 3.6.4 - Cross Site Request Forgery (CSRF) vulnerability), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-124251 (entry last updated 2026-11-10): Affected: - XplodedThemes WPIDE – File Manager & Code Editor: through 3.6.4 Fixed versions: 3.6.5. Conditions (all must be true for the bug to be hit): - WPIDE – File Manager & Code Editor plugin version 3.6.4 and earlier (<= 3.6.4) (source: https://patchstack.com/database/wordpress/plugin/wpide/vulnerability/wordpress-wpide-file-manager-code-editor-plugin-3-6-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, a user action. CISA KEV: CVE-2026-124251 is not listed as of cve.now's last read. This KEV status is for CVE-2026-124251 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://patchstack.com/database/wordpress/plugin/wpide/vulnerability/wordpress-wpide-file-manager-code-editor-plugin-3-6-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve - https://www.cve.org/CVERecord?id=CVE-2026-124251 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-124251 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-124251.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- wpide
through 3.6.4
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124251
Is CVE-2026-124251 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin has a cross-site request forgery flaw, which lets an attacker trick a logged-in user into performing actions they did not intend, such as changing passwords or making purchases.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-124251?
wpide: through 3.6.4.Source: cve.now feed data
Am I affected, and how do I check?
All versions up to and including 3.6.4 of the WPIDE – File Manager & Code Editor plugin are affected, with no earlier starting point listed. Compare the installed plugin version against that range.Source: patchstack.com, cve.org
How do I fix CVE-2026-124251?
Update the WPIDE – File Manager & Code Editor plugin to version 3.6.5 or later.Source: patchstack.com, cve.org