Traffic Monitor: A security weakness
Traffic Monitor is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Traffic Monitor
- Plugin slug
traffic-monitor- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jun 13, 2025
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jun 13, 2025 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Traffic Monitor to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Traffic Monitor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the tfcm_maybe_set_bot_flags() function in all versions up to, and including, 3.2.2. This makes it possible for unauthenticated attackers to disabled bot logging.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N