POSCMS 3.2.18 Syscontroller.php add $data['name'] code injection

Summaryinfo

A vulnerability classified as critical has been found in POSCMS 3.2.18. Impacted is the function Add of the file diy\dayrui\controllers\admin\Syscontroller.php. Performing a manipulation of the argument $data['name'] results in code injection. This vulnerability was named CVE-2018-10236. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in POSCMS 3.2.18. This affects the function add of the file diy\dayrui\controllers\admin\Syscontroller.php. The manipulation of the argument $data['name'] with an unknown input 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:

POSCMS 3.2.18 allows remote attackers to execute arbitrary PHP code via the diy\dayrui\controllers\admin\Syscontroller.php 'add' function because an attacker can control the value of $data['name'] with no restrictions, and this value is written to the FCPATH.$file file.

The bug was discovered 04/19/2018. The weakness was presented 04/19/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-10236 since 04/19/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. Required for exploitation is a authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

By approaching the search of inurl:diy\dayrui\controllers\admin\Syscontroller.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.

See VDB-116912 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• POSCMS

Version

• 3.2.18

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion