Vulnerabilities > Nibbleblog
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-01-27 | CVE-2020-23356 | Improper Authentication vulnerability in Nibbleblog 3.7.1C dmin/kernel/api/login.class.phpin in nibbleblog v3.7.1c allows type juggling for login bypass because == is used instead of === for password hashes, which mishandles hashes that begin with 0e followed by exclusively numerical characters. | 5.0 |
| 2019-02-11 | CVE-2019-7719 | Code Injection vulnerability in Nibbleblog 4.0.5 Nibbleblog 4.0.5 allows eval injection by placing PHP code in the install.php username parameter and then making a content/private/shadow.php request. | 7.5 |
| 2018-09-06 | CVE-2018-16604 | Code Injection vulnerability in Nibbleblog 4.0.5 An issue was discovered in Nibbleblog v4.0.5. | 6.5 |
| 2018-02-01 | CVE-2018-6470 | Information Exposure vulnerability in Nibbleblog 4.0.5 Nibbleblog 4.0.5 on macOS defaults to having .DS_Store in each directory, causing DS_Store information to leak. | 5.0 |
| 2015-09-16 | CVE-2015-6967 | Unspecified vulnerability in Nibbleblog 4.0.1 Unrestricted file upload vulnerability in the My Image plugin in Nibbleblog before 4.0.5 allows remote administrators to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in content/private/plugins/my_image/image.php. | 6.5 |
| 2015-09-16 | CVE-2015-6966 | Cross-Site Request Forgery (CSRF) vulnerability in Nibbleblog 4.0.1 Multiple cross-site request forgery (CSRF) vulnerabilities in Nibbleblog before 4.0.5 allow remote attackers to hijack the authentication of administrators for requests that (1) create a post via a new_simple action to admin.php or (2) conduct cross-site scripting (XSS) attacks via the content parameter in a new_simple action to admin.php. | 6.8 |
| 2014-11-20 | CVE-2014-8996 | Cross-Site Scripting vulnerability in Nibbleblog 4.0.1 Multiple cross-site scripting (XSS) vulnerabilities in Nibbleblog before 4.0.2 allow remote attackers to inject arbitrary web script or HTML via the (1) author_name or (2) content parameter to index.php. | 4.3 |