Security readout for executives and security teams
Plain-English summary
CVE-2026-1215 affects the MMA Call Tracking WordPress plugin through version 2.3.15. If an administrator is tricked into clicking a malicious link or visiting a crafted page while logged in, plugin call tracking settings could be changed. This is an integrity issue, not a direct data theft or site takeover issue based on the provided sources.
Executive priority
Treat as a moderate-priority WordPress plugin issue. It is not reported as actively exploited, and impact appears limited to settings manipulation. Prioritize affected public websites, marketing sites relying on call tracking accuracy, and environments where many administrators manage WordPress from email-linked workflows.
Technical view
The plugin’s `mma_call_tracking_menu` admin settings save path lacks nonce validation, creating a CSRF vulnerability. The CVSS v3.1 score is 4.3, with network attack vector, low complexity, no attacker privileges, and required user interaction. Impact is limited to low integrity modification of plugin configuration settings.
Likely exposure
WordPress sites using MMA Call Tracking versions up to and including 2.3.15 are the relevant exposure. The attacker does not need WordPress credentials, but must induce a logged-in administrator to perform an action. Sites not using this plugin are not affected by this CVE.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation depends on social engineering of an authenticated administrator and would target configuration changes rather than confidentiality or availability. Risk is higher where administrators browse email or external sites while logged into WordPress.
Researcher notes
Sources identify missing nonce validation in the plugin settings save flow on `mma_call_tracking_menu`. The public record states affected versions through 2.3.15, but the supplied affected metadata is sparse. No official patch version is identified in the provided bundle, so remediation status should be confirmed with vendor or repository data.
Mitigation direction
- Check whether MMA Call Tracking is installed and identify its version.
- Review vendor or WordPress plugin guidance for a patched version or official mitigation.
- Update the plugin if a fixed version is available from the vendor.
- Disable or remove the plugin if it is not business-critical.
- Limit WordPress administrator sessions and avoid browsing untrusted links while logged in.
Validation and detection
- Inventory WordPress sites for the MMA Call Tracking plugin.
- Confirm whether installed versions are 2.3.15 or earlier.
- Review plugin settings for unauthorized call tracking configuration changes.
- Check administrative access logs for suspicious timing around settings changes.
- Monitor vendor, Wordfence, and WordPress plugin repository updates for remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1215 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/5689bd2b-1518-4b3b-81a3-cc92575f6c1f?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/mma-call-tracking/trunk/mma_call_tracking.php#L61CVE reference
- https://plugins.trac.wordpress.org/browser/mma-call-tracking/tags/2.3.15/mma_call_tracking.php#L61CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.