DBHcms 1.2.0 mod.page.edit.php $_POST['pageparam_insert_name'] Stored cross site scripting

Summaryinfo

A vulnerability identified as problematic has been detected in DBHcms 1.2.0. This issue affects some unknown processing of the file dbhcms\mod\mod.page.edit.php. Performing a manipulation of the argument $_POST['pageparam_insert_name'] as part of Variable results in cross site scripting (Stored). This vulnerability is reported as CVE-2020-19885. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in DBHcms 1.2.0. It has been classified as problematic. This affects some unknown functionality of the file dbhcms\mod\mod.page.edit.php. The manipulation of the argument $_POST['pageparam_insert_name'] as part of a Variable leads to a cross site scripting vulnerability (Stored). CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

DBHcms v1.2.0 has a stored xss vulnerability as there is no htmlspecialchars function for '$_POST['pageparam_insert_name']' variable in dbhcms\mod\mod.page.edit.php line 227, A remote authenticated with admin user can exploit this vulnerability to hijack other users.

The weakness was disclosed 08/24/2020. This vulnerability is uniquely identified as CVE-2020-19885 since 08/13/2020. It is possible to initiate the attack remotely. A authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

By approaching the search of inurl:dbhcms\mod\mod.page.edit.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.

The entries VDB-160201, VDB-160200, VDB-160199 and VDB-160198 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• DBHcms

Version

• 1.2.0

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion