CVE-2017-1002006

Dtracker <= 1.5 - Missing Authorization

2017-03-13 00:00
Larry W. Cashdollar

Strategic Overview

Status
Unpatched
Affected Plugin
DTracker
Affected Version
<= 1.5
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2017-1002006
View all DTracker vulnerabilities

At a glance

CVE-2017-1002006 is a high-severity Missing Authorization vulnerability in the DTracker WordPress plugin, affecting versions <= 1.5. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2017, reported by Larry W. Cashdollar.

Vulnerability Overview

Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_contact.php doesn't check that the user is authorized before injecting new contacts into the wp_contact table.

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, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Reaching this weakness in DTracker <= 1.5 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for DTracker yet, so installs running <= 1.5 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C