CVE-2026-1215
CSRF Vulnerability in MMA Call Tracking Plugin Allows Settings Modification
Publication date: 2026-02-11
Last updated on: 2026-02-11
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| message_metric | mma_call_tracking | to 2.3.15 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The MMA Call Tracking plugin for WordPress, up to and including version 2.3.15, is vulnerable to a Cross-Site Request Forgery (CSRF) attack. This vulnerability arises because the plugin does not validate a security nonce when saving its configuration on the admin page named `mma_call_tracking_menu`. As a result, an attacker who tricks a site administrator into clicking a malicious link can cause unauthorized changes to the plugin's call tracking configuration settings without the administrator's explicit consent.
How can this vulnerability impact me? :
This vulnerability allows an unauthenticated attacker to modify the call tracking configuration settings of the MMA Call Tracking plugin by exploiting the lack of nonce validation. If an attacker successfully tricks a site administrator into clicking a crafted link, they can alter settings related to phone number tracking and Google AdWords integration. This could disrupt accurate call tracking, potentially leading to incorrect analytics data, loss of tracking functionality, or manipulation of marketing campaign metrics.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves Cross-Site Request Forgery (CSRF) in the MMA Call Tracking WordPress plugin versions up to 2.3.15, due to missing nonce validation when saving plugin configuration on the admin page.'}, {'type': 'paragraph', 'content': 'To detect potential exploitation attempts on your system or network, you can monitor HTTP requests targeting the WordPress admin page related to the MMA Call Tracking plugin, specifically requests to the `mma_call_tracking_menu` admin page that attempt to modify plugin settings.'}, {'type': 'paragraph', 'content': 'Since the plugin logs significant events such as ad clicks and session initialization failures to the PHP error log, reviewing the PHP error logs for unusual or unauthorized configuration changes or suspicious requests may help detect exploitation.'}, {'type': 'paragraph', 'content': 'Suggested commands to help detect suspicious activity include:'}, {'type': 'list_item', 'content': "Using web server access logs, search for POST requests to the MMA Call Tracking admin page (e.g., `mma_call_tracking_menu`):\n`grep 'POST.*mma_call_tracking_menu' /var/log/apache2/access.log`"}, {'type': 'list_item', 'content': "Check PHP error logs for unusual entries related to the plugin:\n`grep -i 'mma_call_tracking' /var/log/php_errors.log`"}, {'type': 'list_item', 'content': "Monitor for unexpected changes in WordPress options related to the plugin by querying the WordPress database:\n`SELECT * FROM wp_options WHERE option_name LIKE '%mma_call_tracking%';`"}, {'type': 'list_item', 'content': 'Use network monitoring tools to detect unusual outbound requests to the Message Metric server URL defined by the plugin, which may indicate plugin activity.'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this Cross-Site Request Forgery vulnerability in the MMA Call Tracking plugin, the immediate step is to update the plugin to a version later than 2.3.15 where the issue is fixed, if available.
If an update is not immediately available, you should restrict access to the WordPress admin pages to trusted users only and ensure administrators do not click on suspicious links that could trigger forged requests.
Additionally, implementing web application firewall (WAF) rules to block unauthorized POST requests to the plugin's admin configuration page can help reduce risk.
Enforcing strong administrator authentication and enabling multi-factor authentication (MFA) will also help prevent unauthorized changes.
Finally, regularly monitor logs for suspicious activity as described in the detection section.