CVE-2017-1002006: Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_contact.php doesn't check that the use

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2017-1002006 is a high-severity flaw (CVSS 7.5) affecting dtracker. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.2% (top 12%)
CISA exploited list	No
Weakness	CWE-862
Published	2017-09-14
Last modified	2026-06-17

Publisher (CNA): Larry Cashdollar · Vendor: dtracker project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-09-14 13:29 UTCPublished CVE record published
2026-06-17 00:59 UTCUpdated Record last modified

dtracker project dtracker DOWNGRADE

Affected: 1.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.5

1. Check installed version

apt-cache policy dtracker || rpm -q dtracker || dtracker --version

2. No fixed release: DOWNGRADE to a release before 1.5 (Debian / Ubuntu)

apt-cache madison dtracker sudo apt install dtracker=<VERSION_BEFORE_1.5> sudo apt-mark hold dtracker

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list dtracker sudo dnf downgrade dtracker-<VERSION_BEFORE_1.5> sudo dnf versionlock add dtracker

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-1002006?

dtracker: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-1002006 being exploited?

CVE-2017-1002006 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-1002006 affect?

CVE-2017-1002006 affects dtracker. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2017-1002006?

Priority 58/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2017-1002007 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_mail.php doesn't check that the user i
CVE-2017-1002005 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, In file ./dtracker/delete.php user input isn't sanitized via
CVE-2017-1002004 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, In file ./dtracker/download.php user input isn't sanitized vi

References

← Back to latest CVEs