VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed May 08, 2017

Better Search TMC Vulnerabilities

Review known vulnerability records for the WordPress plugin Better Search TMC (`better-search-tmc`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2017-1000170, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
1
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing Better Search TMC fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Better Search TMC remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is better-search-tmc before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2017-1000170 High
Vulnerability remediation for Better Search TMC

Affected range: Versions up to 1.0.52. Fixed version is not listed yet.

Priority CVE Quick Links

Fast paths into Better Search TMC CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2017-1000170
JQueryFileTree <= 2.1.5 - Directory Traversal
 Vulnerability Versions up to 1.0.52 No patch listed CVSS 7.5
CVE-2017-1000170 High No patch listed
CVE-2017-1000170 Better Search TMC Vulnerability

JQueryFileTree <= 2.1.5 - Directory Traversal

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Better Search TMC so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 1 high severity finding.
Recent CVEs
CVE-2017-1000170
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Better Search TMC

Sorted by latest disclosure date so newly published issues surface first.

Plugin High Patched: No CVE-2017-1000170
CVE-2017-1000170: JQueryFileTree <= 2.1.5 - Directory Traversal

Several WordPress plugins using the JqueryFileTree extension are vulnerable to Directory Traversal via the 'dir' parameter in various versions. This allows unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

Published
May 08, 2017
Patched Release
Not published
Affected Versions
Versions up to 1.0.52
Next Step
Open the full report for remediation notes and references.
Review CVE-2017-1000170 fixed version details Open CVE Reference