Metronet Tag Manager < 1.2.9 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.2.9
- Affected Plugin
- Metronet Tag Manager
- Affected Version
< 1.2.9- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2018-1000506
At a glance
CVE-2018-1000506 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Metronet Tag Manager WordPress plugin, affecting versions < 1.2.9. 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.2.9; sites on affected versions should update now. Disclosed May 2018, reported by Mallory Adams.
Vulnerability Overview
Metronet Tag Manager version 1.2.7 contains a Cross site Request Forgery (CSRF) vulnerability in Settings page /wp-admin/options-general.php?page=metronet-tag-manager that allows anybody to do almost anything an admin can. This attack appear to be exploitable via Logged in user must following a link. This vulnerability appears to have been fixed in 1.2.9.
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 Metronet Tag Manager < 1.2.9 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 Metronet Tag Manager the fix is 1.2.9: builds < 1.2.9 are affected, anything from 1.2.9 onward is not.
Remediation
Update to version 1.2.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Metronet Tag Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Metronet Tag Manager 1.2.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C