To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Documentation: Home / Vulnerabilities / Input validation vulnerability in Comment Extra Fields 1.7
Latest
Protecting site visitors with Security Headers
Hardening your website’s security
Login protection as essential security
Why WordPress is (in)secure
Staying ahead of vulnerabilities
Password has been found in a data breach
Input validation vulnerability in Comment Extra Fields 1.7
The Comment Extra Fields plugin for WordPress, up to version 1.7, is vulnerable to Cross-Site Scripting. This means that attackers can inject malicious web scripts in a victim’s browser that can be executed. This is caused by the plugin not properly sanitizing the inputs or escaping the outputs of the swfupload.swf file.
Detected in:
This information is sourced from www.wpvulnerability.com. An open-source database of vulnerabilities maintained by the community. Help us out by submitting vulnerabilities!
Version compare shows which versions have a vulnerability. For example: >= 2.2.8 <= 2.2.21 means:
> from 2.2.8
= including 2.2.8 & 2.2.21
< to 2.2.21
Is this information incorrect? Please leave us a message.