HomeWordPress vulnerabilitiesWPIDE
WPIDE vulnerabilities
WPIDE has 4 known vulnerabilities in this database. The most recent published record is dated 15 Oct 2024.
- Known vulnerabilities
- 4
- Active installs
- 40,000+
- Latest version
- 3.5.9
- Last updated
- 16 Sep 2026
- Most recent
- 15 Oct 2024
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2024-9546 | Medium 5.3 | Before 3.5.0 | Fixed in 3.5.0 | 15 Oct 2024 |
| Arbitrary file upload CVE-2022-40217 | Medium 6.5 | Up to 2.6 | Fixed in a later version (latest 3.5.9) | 21 Sep 2022 |
| File inclusion CVE-2022-2261 | High 7.2 | Before 3.0 | Fixed in 3.0 | 29 Aug 2022 |
| Arbitrary file read CVE-2022-35235 | Medium 4.9 | Before 3.0 | Fixed in 3.0 | 23 Aug 2022 |
Read the published descriptions
- CVE-2024-9546, 15 Oct 2024
- The WPIDE - File Manager & Code Editor plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.9. This is due to the plugin utilizing the PHP-Parser library, which outputs parser rebuild command execution results. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website. CVE record
- CVE-2022-40217, 21 Sep 2022
- Authenticated (admin+) Arbitrary File Edit/Upload vulnerability in XplodedThemes WPide plugin <= 2.6 at WordPress. CVE record
- CVE-2022-2261, 29 Aug 2022
- The WPIDE WordPress plugin before 3.0 does not sanitize and validate the filename parameter before using it in a require statement in the admin dashboard, leading to a Local File Inclusion issue. CVE record
- CVE-2022-35235, 23 Aug 2022
- Authenticated (admin+) Arbitrary File Read vulnerability in XplodedThemes WPide plugin <= 2.6 at WordPress. CVE record
What to do if you run WPIDE
If you run WPIDE, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WPIDE vulnerabilities
Free. We email you when a new vulnerability is published for WPIDE, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.