A-Blog CMS up to 2.8.64/2.9.26/2.10.23 injection

Summaryinfo

A vulnerability classified as problematic was found in A-Blog CMS up to 2.8.64/2.9.26/2.10.23. This issue affects some unknown processing. The manipulation results in injection. This vulnerability is identified as CVE-2019-6034. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in A-Blog CMS up to 2.8.64/2.9.26/2.10.23 (Blog Software). Affected is an unknown function. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on integrity. CVE summarizes:

a-blog cms versions prior to Ver.2.10.23 (Ver.2.10.x), Ver.2.9.26 (Ver.2.9.x), and Ver.2.8.64 (Ver.2.8.x) allows arbitrary scripts to be executed in the context of the application due to unspecified vectors.

The weakness was released 12/26/2019. This vulnerability is traded as CVE-2019-6034 since 01/10/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1055.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Entry connected to this vulnerability is available at VDB-147755. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Blog Software

Name

• A-Blog CMS

Version

• 2.8.0
• 2.8.1
• 2.8.2
• 2.8.3
• 2.8.4
• 2.8.5
• 2.8.6
• 2.8.7
• 2.8.8
• 2.8.9
• 2.8.10
• 2.8.11
• 2.8.12
• 2.8.13
• 2.8.14
• 2.8.15
• 2.8.16
• 2.8.17
• 2.8.18
• 2.8.19
• 2.8.20
• 2.8.21
• 2.8.22
• 2.8.23
• 2.8.24
• 2.8.25
• 2.8.26
• 2.8.27
• 2.8.28
• 2.8.29
• 2.8.30
• 2.8.31
• 2.8.32
• 2.8.33
• 2.8.34
• 2.8.35
• 2.8.36
• 2.8.37
• 2.8.38
• 2.8.39
• 2.8.40
• 2.8.41
• 2.8.42
• 2.8.43
• 2.8.44
• 2.8.45
• 2.8.46
• 2.8.47
• 2.8.48
• 2.8.49
• 2.8.50
• 2.8.51
• 2.8.52
• 2.8.53
• 2.8.54
• 2.8.55
• 2.8.56
• 2.8.57
• 2.8.58
• 2.8.59
• 2.8.60
• 2.8.61
• 2.8.62
• 2.8.63
• 2.8.64
• 2.9.0
• 2.9.1
• 2.9.2
• 2.9.3
• 2.9.4
• 2.9.5
• 2.9.6
• 2.9.7
• 2.9.8
• 2.9.9
• 2.9.10
• 2.9.11
• 2.9.12
• 2.9.13
• 2.9.14
• 2.9.15
• 2.9.16
• 2.9.17
• 2.9.18
• 2.9.19
• 2.9.20
• 2.9.21
• 2.9.22
• 2.9.23
• 2.9.24
• 2.9.25
• 2.9.26
• 2.10.0
• 2.10.1
• 2.10.2
• 2.10.3
• 2.10.4
• 2.10.5
• 2.10.6
• 2.10.7
• 2.10.8
• 2.10.9
• 2.10.10
• 2.10.11
• 2.10.12
• 2.10.13
• 2.10.14
• 2.10.15
• 2.10.16
• 2.10.17
• 2.10.18
• 2.10.19
• 2.10.20
• 2.10.21
• 2.10.22
• 2.10.23

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion