Show filters
49 Total Results
Displaying 31-40 of 49
Sort by:
Attacker Value
Unknown

CVE-2018-9206

Disclosure Date: October 11, 2018 (last updated November 27, 2024)
Unauthenticated arbitrary file upload vulnerability in Blueimp jQuery-File-Upload <= v9.22.0
Attacker Value
Unknown

PHP forms generated using the PHP FormMail Generator are vulnerable to stored c…

Disclosure Date: July 13, 2018 (last updated November 27, 2024)
The code generated by PHP FormMail Generator prior to 17 December 2016 is vulnerable to stored cross-site scripting. In the generated form.lib.php file, upload file types are checked against a hard-coded list of dangerous extensions. This list does not include all variations of PHP files, which may lead to execution of the contained PHP code if the attacker can guess the uploaded filename. The form by default appends a short random string to the end of the filename.
0
Attacker Value
Unknown

PHP FormMail Generator generates PHP code for standard web forms, and the code …

Disclosure Date: July 13, 2018 (last updated November 27, 2024)
The PHP form code generated by PHP FormMail Generator deserializes untrusted input as part of the phpfmg_filman_download() function. A remote unauthenticated attacker may be able to use this vulnerability to inject PHP code, or along with CVE-2016-9484 to perform local file inclusion attacks and obtain files from the server.
0
Attacker Value
Unknown

PHP FormMail Generator generates PHP code for standard web forms, and the code …

Disclosure Date: July 13, 2018 (last updated November 27, 2024)
Code generated by PHP FormMail Generator may allow a remote unauthenticated user to bypass authentication in the to access the administrator panel by navigating directly to /admin.php?mod=admin&func=panel
0
Attacker Value
Unknown

PHP FormMail Generator generates PHP code for standard web forms, and the code …

Disclosure Date: July 13, 2018 (last updated November 27, 2024)
The generated PHP form code does not properly validate user input folder directories, allowing a remote unauthenticated attacker to perform a path traversal and access arbitrary files on the server. The PHP FormMail Generator website does not use version numbers and is updated continuously. Any PHP form code generated by this website prior to 2016-12-06 may be vulnerable.
0
Attacker Value
Unknown

PHP forms generated using the PHP FormMail Generator are vulnerable to unrestri…

Disclosure Date: July 13, 2018 (last updated November 27, 2024)
The code generated by PHP FormMail Generator prior to 17 December 2016 is vulnerable to unrestricted upload of dangerous file types. In the generated form.lib.php file, upload file types are checked against a hard-coded list of dangerous extensions. This list does not include all variations of PHP files, which may lead to execution of the contained PHP code if the attacker can guess the uploaded filename. The form by default appends a short random string to the end of the filename.
0
Attacker Value
Unknown

CVE-2017-16045

Disclosure Date: June 04, 2018 (last updated November 26, 2024)
`jquery.js` was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.
0
Attacker Value
Unknown

CVE-2018-1325

Disclosure Date: April 18, 2018 (last updated November 26, 2024)
In Apache wicket-jquery-ui <= 6.29.0, <= 7.10.1, <= 8.0.0-M9.1, JS code created in WYSIWYG editor will be executed on display.
0
Attacker Value
Unknown

CVE-2017-15719

Disclosure Date: March 12, 2018 (last updated November 26, 2024)
In Wicket jQuery UI 6.28.0 and earlier, 7.9.1 and earlier, and 8.0.0-M8 and earlier, a security issue has been discovered in the WYSIWYG editor that allows an attacker to submit arbitrary JS code to WYSIWYG editor.
0
Attacker Value
Unknown

CVE-2012-6708

Disclosure Date: January 18, 2018 (last updated November 08, 2023)
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
0