Dtracker
dtracker · plugin
Known security vulnerabilities for Dtracker. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
4 exploitable without logging in · latest Sep 14, 2017
Closed on wordpress.org
Removed from the directory on Jan 15, 2011 · reason: no reason given. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 7.5
CVE-2017-1002007unauthenticated→ 1.5
Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_mail.php doesn't check that the user is authorized before injecting
- High 7.5
CVE-2017-1002006unauthenticated→ 1.5
Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_contact.php doesn't check that the user is authorized before injecti
- High 7.5
CVE-2017-1002005unauthenticated→ 1.5
Vulnerability in wordpress plugin DTracker v1.5, In file ./dtracker/delete.php user input isn't sanitized via the contact_id variable before
- High 7.5
CVE-2017-1002004unauthenticated→ 1.5
Vulnerability in wordpress plugin DTracker v1.5, In file ./dtracker/download.php user input isn't sanitized via the id variable before addin
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).