awesome-support Plugin up to 3.1.6 on WordPress Shortcode Reply 7pk security

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.3$0-$5k0.00

Summaryinfo

A vulnerability was found in awesome-support Plugin up to 3.1.6 on WordPress. It has been rated as critical. Impacted is an unknown function of the component Shortcode Handler. Performing a manipulation as part of Reply results in 7pk security. This vulnerability was named CVE-2015-9318. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in awesome-support Plugin up to 3.1.6 on WordPress (WordPress Plugin). It has been classified as critical. This affects an unknown function of the component Shortcode Handler. The manipulation as part of a Reply leads to a 7pk security vulnerability. CWE is classifying the issue as CWE-254. This is going to have an impact on integrity. The summary by CVE is:

The awesome-support plugin before 3.1.7 for WordPress has a security issue in which shortcodes are allowed in replies.

The weakness was presented 08/20/2019. This vulnerability is uniquely identified as CVE-2015-9318 since 08/15/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1211 according to MITRE ATT&CK.

Upgrading to version 3.1.7 eliminates this vulnerability.

See VDB-140342 for similar entry. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: 7pk security
CWE: CWE-254
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: awesome-support Plugin 3.1.7

Timelineinfo

08/15/2019 🔍
08/20/2019 +5 days 🔍
08/21/2019 +1 days 🔍
11/27/2023 +1559 days 🔍

Sourcesinfo

Advisory: wordpress.org
Status: Not defined

CVE: CVE-2015-9318 (🔍)
GCVE (CVE): GCVE-0-2015-9318
GCVE (VulDB): GCVE-100-140343
See also: 🔍

Entryinfo

Created: 08/21/2019 06:57
Updated: 11/27/2023 08:16
Changes: 08/21/2019 06:57 (38), 08/01/2020 06:39 (18), 11/27/2023 08:16 (4)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!