PatchFirst · Latest vulnerabilities
Vulnerabilities published for froxlor/froxlor in the last 30 days: 0. Listed in the KEV catalogue: 0.
Vulnerabilities: 60
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in froxlor/froxlor prior to 2.0.10.
Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.10.
Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10.
Path Traversal: '\..\filename' in GitHub repository froxlor/froxlor prior to 2.0.0.
Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.
Improper Authorization in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Argument Injection in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Code Injection in GitHub repository froxlor/froxlor prior to 0.10.38.2.
Code Injection in GitHub repository froxlor/froxlor prior to 0.10.39.
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 0.10.38.
Froxlor through 0.10.22 does not perform validation on user input passed in the customermail GET parameter. The value of this parameter is reflected in the login webpage, allowing the injection of arbitrary HTML tags.
Multiple cross-site scripting (XSS) vulnerabilities in the Customer Add module of Foxlor v0.10.16 allows attackers to execute arbitrary web scripts or HTML via a crafted payload entered into the name, firstname, or username input fields.
Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name.
An issue was discovered in Froxlor before 0.10.14. Remote attackers with access to the installation routine could have executed arbitrary code via the database configuration options that were passed unescaped to exec, because of _backupExistingDatabase in install/lib/class.FroxlorInstall.php.
An issue was discovered in Froxlor through 0.10.15. The installer wrote configuration parameters including passwords into files in /tmp, setting proper permissions only after writing the sensitive data. A local attacker could have disclosed the information if he read the file at the right time, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.
An issue was discovered in Froxlor before 0.10.14. It created files with static names in /tmp during installation if the installation directory was not writable. This allowed local attackers to cause DoS or disclose information out of the config files, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.
Froxlor version <= 0.9.39.5 contains a PHP Object Injection vulnerability in Domain name form that can result in Possible information disclosure and remote code execution. This attack appear to be exploitable via Passing malicious PHP objection in $_POST['ssl_ipandport']. This vulnerability appears to have been fixed in after commit c1e62e6.
Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.
Froxlor before 0.9.35 uses the PHP rand function for random number generation, which makes it easier for remote attackers to guess the password reset token by predicting a value.
Check your installed stack and versions against the current vulnerability feeds.