CVE-2021-26776

CSZ CMS 1.2.9 is affected by a cross-site scripting XSS vulnerability in multiple pages through the field name...

CVE-2021-27678

Cross-site scripting XSS vulnerability in Snippets in Batflat CMS 1.3.6 allows remote attackers to inject arbitrary web script or HTML via the field name...

Cross site scripting

CSZ CMS 1.2.9 is affected by a cross-site scripting XSS vulnerability in multiple pages through the field name...

CVE-2021-26776

CSZ CMS 1.2.9 is affected by a cross-site scripting XSS vulnerability in multiple pages through the field name...

CVE-2021-27678

Cross-site scripting XSS vulnerability in Snippets in Batflat CMS 1.3.6 allows remote attackers to inject arbitrary web script or HTML via the field name...

CVE-2021-26776

CSZ CMS 1.2.9 is affected by a cross-site scripting XSS vulnerability in multiple pages through the field name...

CSZ CMS 跨站脚本漏洞

CSZ CMS is an open source content management system. A cross-site scripting vulnerability exists in several pages of CSZ CMS 1.2.9. The vulnerability can be exploited to conduct cross-site scripting attacks via field names...

Paweł Klockiewicz Batflat CMS 跨站脚本漏洞

Batflat is a simple, lightweight content management system CMS. A cross-site scripting vulnerability exists in "Navigation" in Batflat 1.3.6, which can be exploited by remote attackers to inject arbitrary web script or HTML via a field name...

MantisBT 跨站脚本漏洞

MantisBT is MantisBT Mantisbt team of a Web-based open source defect tracking system . The system provides project management and defect tracking services in the form of Web operations. A security vulnerability exists in MantisBT 2.24.3 and earlier versions, which stems from a custom field name n...

CVE-2020-29477

Invision Community 4.5.4 is affected by cross-site scripting XSS in the Field Name field. This vulnerability can allow an attacker to inject the XSS payload in Field Name and each time any user will open that, the XSS triggers and the attacker can able to steal the cookie according to the crafted...

CVE-2020-29477

Invision Community 4.5.4 is affected by cross-site scripting XSS in the Field Name field. This vulnerability can allow an attacker to inject the XSS payload in Field Name and each time any user will open that, the XSS triggers and the attacker can able to steal the cookie according to the crafted...

Cross site scripting

Invision Community 4.5.4 is affected by cross-site scripting XSS in the Field Name field. This vulnerability can allow an attacker to inject the XSS payload in Field Name and each time any user will open that, the XSS triggers and the attacker can able to steal the cookie according to the crafted...

CVE-2020-29477

Invision Community 4.5.4 is affected by cross-site scripting XSS in the Field Name field. This vulnerability can allow an attacker to inject the XSS payload in Field Name and each time any user will open that, the XSS triggers and the attacker can able to steal the cookie according to the crafted...

Invision Community 4.5.4 Cross Site Scripting

Exploit Title: Invision Community 4.5.4 - 'Field Name' Stored Cross-Site Scripting Date: 02-12-2020 Exploit Author: Hemant Patidar HemantSolo Vendor Homepage: https://invisioncommunity.com/ Software Link: https://invisioncommunity.com/buy Version: 4.5.4 Tested on: Windows 10/Kali Linux Vulnerable...

Invision Community 4.5.4 - 'Field Name' Stored Cross-Site Scripting

Exploit Title: Invision Community 4.5.4 - 'Field Name' Stored Cross-Site Scripting Date: 02-12-2020 Exploit Author: Hemant Patidar HemantSolo Vendor Homepage: https://invisioncommunity.com/ Software Link: https://invisioncommunity.com/buy Version: 4.5.4 Tested on: Windows 10/Kali Linux CVE:...

CVE-2020-1710

The issue appears to be that JBoss EAP 6.4.21 does not parse the field-name in accordance to RFC72301 as it returns a 200 instead of a 400...

Design/Logic Flaw

The issue appears to be that JBoss EAP 6.4.21 does not parse the field-name in accordance to RFC72301 as it returns a 200 instead of a 400...

EAP: field-name is not parsed in accordance to RFC7230

A flaw was discovered in JBoss EAP, where it does not process the header field-name in accordance with RFC7230. Whitespace between the header field-name and colon is processed, resulting in an HTTP response code of 200 instead of a bad request of 400...

EAP: field-name is not parsed in accordance to RFC7230

A flaw was discovered in JBoss EAP, where it does not process the header field-name in accordance with RFC7230. Whitespace between the header field-name and colon is processed, resulting in an HTTP response code of 200 instead of a bad request of 400...

EAP: field-name is not parsed in accordance to RFC7230

A flaw was discovered in JBoss EAP, where it does not process the header field-name in accordance with RFC7230. Whitespace between the header field-name and colon is processed, resulting in an HTTP response code of 200 instead of a bad request of 400...