This information is sourced from wpvulnerabilities.com. An open-source database of vulnerabilities maintained by the community. Help us out by submitting vulnerabilities!
A plugin called WP JobHunt, which is used with the JobCareer theme on WordPress, has a security issue. This issue allows attackers who have a certain level of access to add harmful code to web pages....
Read MoreThe JobCareer theme's WP JobHunt plugin for WordPress has a security issue in versions 7.6 and below. This allows unauthorized users with Candidate or Employer access to log in to the site, even if t...
Read MoreThe WP JobHunt plugin for WordPress has a security issue that affects all versions up to version 7.1. This issue is known as Insecure Direct Object Reference and it occurs because the plugin does not...
Read MoreThe WP JobHunt plugin for WordPress has a security issue that can affect all versions up to 7.2. This vulnerability is called Insecure Direct Object Reference and is caused by a function called cs_re...
Read MoreThe WP JobHunt plugin for WordPress has a security issue that allows unauthorized access to user accounts. This is because a function called wp_ajax_google_api_login_callback does not properly check ...
Read MoreThe WP JobHunt plugin for WordPress has a security issue that could allow unauthorized access to user accounts. This is because the plugin does not properly check a user's identity before making chan...
Read MoreThe WP JobHunt plugin for WordPress has a security issue that allows unauthorized users to take over someone else's account. This can happen because the plugin does not check a user's identity before...
Read MoreThe WP JobHunt plugin for WordPress has a security issue that allows attackers to bypass the authentication process. This means that they can gain access to any user's account without being verified...
Read MoreThe WP-jobhunt plugin for WordPress
Read MoreThe WP-jobhunt plugin for WordPress had a security issue that allowed someone who wasn't authorized to access it to reset the password of a user's account. This issue was fixed in version 2.4.
Read More