Axublog 1.1.0 cmsconfig.php webkeywords code injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Axublog 1.1.0. This issue affects some unknown processing of the file cmsconfig.php. Performing a manipulation of the argument webkeywords as part of Parameter results in code injection. This vulnerability was named CVE-2018-10740. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in Axublog 1.1.0. This affects an unknown functionality of the file cmsconfig.php. The manipulation of the argument webkeywords as part of a Parameter leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Axublog 1.1.0 allows remote Code Execution as demonstrated by injection of PHP code (contained in the webkeywords parameter) into the cmsconfig.php file.

The bug was discovered 05/04/2018. The weakness was presented 05/04/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2018-10740 since 05/04/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

By approaching the search of inurl:cmsconfig.php it is possible to find vulnerable targets with Google Hacking.

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Axublog

Version

• 1.1.0

Website

• Product: https://github.com/axublog/axublog/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion