WP Coder – Code Snippets + HTML, CSS, JS and PHP Injection <= 3.6.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.6.1
- Affected Plugin
- WP Coder – Insert & Manage Code Snippets
- Affected Version
<= 3.6- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-24699
At a glance
CVE-2025-24699 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Coder WordPress plugin, affecting versions <= 3.6. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.6.1; sites on affected versions should update now. Disclosed January 2025, reported by 0xd4rk5id3.
Vulnerability Overview
The WP Coder – Code Snippets + HTML, CSS, JS and PHP Injection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WP Coder <= 3.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Coder the fix is 3.6.1: builds <= 3.6 are affected, anything from 3.6.1 onward is not.
Remediation
Update to version 3.6.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Coder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Coder 3.6.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Coder – Insert & Manage Code Snippets
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C