Wpcode
Monthly
Unauthenticated visitors can suppress all auto-inserted snippets for their own requests on WordPress sites running the WPCode plugin before 2.4.0, because the plugin enters its snippet "safe mode" without correctly verifying that the incoming request is genuinely for the login screen. The effect is confined to the attacker's own requests - snippets still execute for every other visitor and no site-wide change occurs - so per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3) the result is a low-severity bypass of snippet-enforced behavior (headers, redirects, content/access controls) rather than an outage or global configuration change. Publicly available exploit code exists (WPScan advisory), and there is no CISA KEV confirmation of active exploitation, so real-world priority is modest despite WPCode's wide deployment.
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. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
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. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
The WPCode WordPress plugin before 2.0.7 does not have adequate privilege checks in place for several AJAX actions, only checking the nonce. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Unauthenticated visitors can suppress all auto-inserted snippets for their own requests on WordPress sites running the WPCode plugin before 2.4.0, because the plugin enters its snippet "safe mode" without correctly verifying that the incoming request is genuinely for the login screen. The effect is confined to the attacker's own requests - snippets still execute for every other visitor and no site-wide change occurs - so per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3) the result is a low-severity bypass of snippet-enforced behavior (headers, redirects, content/access controls) rather than an outage or global configuration change. Publicly available exploit code exists (WPScan advisory), and there is no CISA KEV confirmation of active exploitation, so real-world priority is modest despite WPCode's wide deployment.
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. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
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. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
The WPCode WordPress plugin before 2.0.7 does not have adequate privilege checks in place for several AJAX actions, only checking the nonce. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.