CM Ad Changer <= 1.7.7 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.7.8
- Affected Version
<= 1.7.7- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the CM Ad Changer WordPress plugin, affecting versions <= 1.7.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7.8; sites on affected versions should update now. Disclosed June 2016, reported by Aaditya Purani.
Vulnerability Overview
The CM Ad Changer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Banner Title field in versions up to, and including, 1.7.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, granted they can trick a site's 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in CM Ad Changer <= 1.7.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 1.7.8: builds <= 1.7.7 are affected, anything from 1.7.8 onward is not.
Remediation
Update to version 1.7.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 1.7.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