HomeWordPress vulnerabilitiesWPCode
WPCode vulnerabilities
WPCode has 4 known vulnerabilities in this database. The most recent published record is dated 27 May 2026.
- Known vulnerabilities
- 4
- Active installs
- 3m+
- Latest version
- 2.3.9
- Last updated
- 27 Aug 2026
- Most recent
- 27 May 2026
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 |
|---|---|---|---|---|
| Remote code execution CVE-2026-8832 | High 8.8 | Up to 2.3.5 | Fixed in a later version (latest 2.3.9) | 27 May 2026 |
| Cross-site scripting (XSS) CVE-2023-3524 | Medium 6.1 | Up to 2.0.13.1 | Fixed in a later version (latest 2.3.9) | 7 Aug 2023 |
| Cross-site request forgery (CSRF) CVE-2023-1624 | Medium 6.5 | Before 2.0.9 | Fixed in 2.0.9 | 24 Apr 2023 |
| Broken access control CVE-2023-0328 | Medium 4.3 | Before 2.0.7 | Fixed in 2.0.7 | 6 Mar 2023 |
Read the published descriptions
- CVE-2026-8832, 27 May 2026
- The WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 2.3.5 This is due to the 'wpcode' custom post type being registered without a custom capability_type or capability restrictions in the wpcode_register_post_type() function, allowing WordPress core to fall back to standard post capabilities for all creation paths including XML-RPC. This makes it possible for authenticated attackers, with author-level access and above, to create and publish executable PHP snippet posts via XML-RPC wp.newPost, which are then executed server-side via eval() in the run_eval() function when the snippet is rendered through the [wpcode] shortcode. CVE record
- CVE-2023-3524, 7 Aug 2023
- The WPCode WordPress plugin before 2.0.13.1 does not escape generated URLs before outputting them in attributes, leading to Reflected Cross-Site Scripting CVE record
- CVE-2023-1624, 24 Apr 2023
- The WPCode WordPress plugin before 2.0.9 has a flawed CSRF when deleting log, and does not ensure that the file to be deleted is inside the expected folder. This could allow attackers to make users with the wpcode_activate_snippets capability delete arbitrary log files on the server, including outside of the blog folders CVE record
- CVE-2023-0328, 6 Mar 2023
- The WPCode WordPress plugin before 2.0.7 does not have adequate privilege checks in place for several AJAX actions, only checking the nonce. This may lead to allowing any authenticated user who can edit posts to call the endpoints related to WPCode Library authentication (such as update and delete the auth key). CVE record
What to do if you run WPCode
If you run WPCode, 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 WPCode vulnerabilities
Free. We email you when a new vulnerability is published for WPCode, 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.