Matthew Kienow

A stored XSS issue is present in the document "note" functionality of OpenKM, accessible if an attacker has console access and is authenticated.

The OpenKM DMS is vulnerable to a stored (persistent, or "Type II") XSS condition when a malicious document provided by an attacker is processed.

An XSS issue was discovered in the Mayan EDMS DMS, where successful exploitation was observed in the in-product tagging system.

The issue is a stored cross-site scripting (XSS) condition in the document version comments, which allows for persistent or "Type II" XSS attacks. This means that an attacker can inject malicious code into the comments of a document version, and this code will be executed when other users view the comments.

The issue is a stored cross-site scripting (XSS) condition, specifically a "Type II" or persistent XSS, that occurs in the document file name. This means that an attacker could potentially inject malicious scripts into the file names of documents, which would then be executed when the file name is displayed or processed.

The issue is a stored cross-site scripting (XSS) condition in the in-app chat system. This type of XSS occurs when malicious code is stored on the server and then executed by the browser when the affected page is viewed.

The issue is related to a stored cross-site scripting (XSS) condition in the in-app messaging system, affecting both subject and message bodies. This type of XSS is also known as "Type II" or persistent XSS, meaning the malicious script is stored on the server and can be executed by multiple users.

The issue is related to a stored cross-site scripting (XSS) condition. This occurs when a malicious document provided by an attacker is used, allowing for potential exploitation. The vulnerability exists due to insufficient encryption of user-input data. Successful exploitation can enable an attacker to perform cross-site scripting attacks. There is also mention of an XSS vulnerability in the Mayan EDMS DMS, specifically observed in the in-product tagging system.

The issue is related to a stored XSS problem due to insufficient filtering of SNMP agent supplied data. An attacker can create a malicious SNMP `sysName` or `sysContact` response to store an XSS payload, which will trigger when a user views the data in the web UI.

The issue is related to a stored XSS problem due to insufficient filtering of SNMP trap supplied data. An attacker can create a malicious SNMP trap to store an XSS payload, which will trigger when a user views the events list page in the web UI.

Name of the Vulnerable Software and Affected Versions: HP PageWide Printers versions prior to firmware 1708D HP OfficeJet Pro Printers versions prior to firmware 1708D Description: A potential security issue has been identified that could potentially be exploited to execute arbitrary code. Recommendations: For HP PageWide Printers versions prior to firmware 1708D, update the firmware to version 1708D or later. For HP OfficeJet Pro Printers versions prior to firmware 1708D, update the firmware to version 1708D or later.

The issue concerns command injection via certain commands in the tools.pl CGI script. The affected commands include man, finger, ping, trace, and nslookup.

The issue is related to a security problem where an attacker can exploit the software using SNMP, leading to XSS.

The issue allows for XSS via SNMP.

The issue is related to a security problem where an SNMP response can lead to XSS.

The issue allows remote attackers to obtain sensitive information, including credentials, keys, and SSID details, by sending an SNMP request. This is possible due to the use of a default SNMP community string set to `public`.

The issue allows remote attackers to obtain sensitive information, including password, key, and SSID details, by sending an SNMP request. This is possible due to the use of a default SNMP community string set to `public`.