CM Ad Changer <= 2.0.7 - Cross-Site Request Forgery to Campaign Deletion via Campaign Management
Strategic Overview
- Status
- Patched in 2.0.8
- Affected Version
<= 2.0.7- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-9236
At a glance
CVE-2026-9236 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the CM Ad Changer WordPress plugin, affecting versions <= 2.0.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.8; sites on affected versions should update now. Disclosed May 2026, reported by jamaal.
Vulnerability Overview
The CM Ad Changer – A simple tool to control and optimize your site's banners plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.7. This is due to missing or incorrect nonce validation on the cmac_campaigns_action function. This makes it possible for unauthenticated attackers to permanently delete arbitrary advertising campaigns, including their associated banner records and uploaded files 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 CM Ad Changer <= 2.0.7 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 CM Ad Changer the fix is 2.0.8: builds <= 2.0.7 are affected, anything from 2.0.8 onward is not.
Remediation
Update to version 2.0.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to CM Ad Changer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CM Ad Changer 2.0.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in CM Ad Changer – A simple tool to control and optimize your site's banners
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C