wp-support-plus-responsive-ticket-system Plugin up to 4.1 on WordPress path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in wp-support-plus-responsive-ticket-system Plugin up to 4.1 on WordPress. The affected element is an unknown function. The manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2014-10390. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in wp-support-plus-responsive-ticket-system Plugin up to 4.1 on WordPress (Ticket Tracking Software). It has been rated as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has directory traversal.
The weakness was disclosed 08/22/2019. The identification of this vulnerability is CVE-2014-10390 since 08/22/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 4.2 eliminates this vulnerability.
The entries VDB-140598, VDB-140596, VDB-140595 and VDB-140594 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: wp-support-plus-responsive-ticket-system Plugin 4.2
Timeline
08/22/2019 🔍08/22/2019 🔍
08/23/2019 🔍
08/03/2020 🔍
Sources
Status: Not definedCVE: CVE-2014-10390 (🔍)
GCVE (CVE): GCVE-0-2014-10390
GCVE (VulDB): GCVE-100-140597
See also: 🔍
Entry
Created: 08/23/2019 07:06Updated: 08/03/2020 10:17
Changes: 08/23/2019 07:06 (37), 08/03/2020 10:17 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.