P5 FNIP-8x16A/FNIP-4xSH 1.0.11/1.0.20 config.html lab4 cross site scripting

Summaryinfo

A vulnerability has been found in P5 FNIP-8x16A and FNIP-4xSH 1.0.11/1.0.20 and classified as problematic. This impacts an unknown function of the file config.html. Performing a manipulation of the argument lab4 results in cross site scripting. This vulnerability is cataloged as CVE-2020-37148. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in P5 FNIP-8x16A and FNIP-4xSH 1.0.11/1.0.20. This affects an unknown part of the file config.html. The manipulation of the argument lab4 with an unknown input leads to a cross site scripting vulnerability. 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:

P5 FNIP-8x16A/FNIP-4xSH versions 1.0.20 and 1.0.11 suffer from a stored cross-site scripting vulnerability. Input passed to several GET/POST parameters is not properly sanitized before being returned to the user, allowing attackers to execute arbitrary HTML and script code in a user's browser session in the context of the affected site. This can be exploited by submitting crafted input to the label modification functionality, such as the 'lab4' parameter in config.html.

The weakness was shared by Gjoko Krstic as ZSL-2020-5564. The advisory is shared at zeroscience.mk. This vulnerability is uniquely identified as CVE-2020-37148 since 02/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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:config.html 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.

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

Productinfo

Vendor

• P5

Name

• FNIP-4xSH
• FNIP-8x16A

Version

• 1.0.11
• 1.0.20

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