firefly-iii firefly iii vulnerabilities, newest first
Filter
By year: all 2026 2025 2024 2023 2022 2021
- 6.1CVE-2024-22075EPSS 0.3%
Firefly III (aka firefly-iii) before 6.1.1 allows webhooks HTML Injection.
- 9.8CVE-2023-1788EPSS 0.4%
Insufficient Session Expiration in GitHub repository firefly-iii/firefly-iii prior to 6.
- 9.8CVE-2023-1789EPSS 0.3%
Improper Input Validation in GitHub repository firefly-iii/firefly-iii prior to 6.0.0.
- 6.5CVE-2023-0298EPSS 0.7%
Incorrect Authorization in GitHub repository firefly-iii/firefly-iii prior to 5.8.0.
- 4.3CVE-2021-4005EPSS 0.4%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 4.3CVE-2021-4015EPSS 0.4%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 4.3CVE-2021-3921EPSS 0.4%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 8.8CVE-2021-3901EPSS 0.6%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 6.5CVE-2021-3900EPSS 0.6%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 5.4CVE-2021-3851EPSS 0.6%
firefly-iii is vulnerable to URL Redirection to Untrusted Site
- 8.8CVE-2021-3846EPSS 0.8%
firefly-iii is vulnerable to Unrestricted Upload of File with Dangerous Type
- 8.8CVE-2021-3819EPSS 0.5%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 6.5CVE-2021-3730EPSS 0.5%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 4.3CVE-2021-3729EPSS 0.4%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 6.5CVE-2021-3728EPSS 0.5%
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
- 7.5CVE-2021-3663EPSS 0.7%
firefly-iii is vulnerable to Improper Restriction of Excessive Authentication Attempts
- 5.4CVE-2019-14672EPSS 0.7%
Firefly III 4.7.17.5 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the liability name field. The JavaScript code is executed upon an error condition during a visit to the account show page.
- 3.3CVE-2019-14671EPSS 0.5%
Firefly III 4.7.17.3 is vulnerable to local file enumeration. An attacker can enumerate local files due to the lack of protocol scheme sanitization, such as for file:/// URLs. This is related to fints_url to import/job/configuration, and i…
- 5.4CVE-2019-14670EPSS 0.8%
Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the bill name field. The JavaScript code is executed during rule-from-bill creation.
- 5.4CVE-2019-14669EPSS 0.8%
Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the asset account name. The JavaScript code is executed during a visit to the audit account statistics page.
- 5.4CVE-2019-14668EPSS 0.8%
Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the transaction description field. The JavaScript code is executed during deletion of a transaction link.
- 6.1CVE-2019-14667EPSS 1.3%
Firefly III 4.7.17.4 is vulnerable to multiple stored XSS issues due to the lack of filtration of user-supplied data in the transaction description field and the asset account name. The JavaScript code is executed during a convert transact…
- 5.4CVE-2019-13647EPSS 0.7%
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file content. The JavaScript code is executed during attachments/view/$file_id$ attachment viewing. NOTE: It is asserted that …
- 5.4CVE-2019-13646EPSS 0.7%
Firefly III before 4.7.17.3 is vulnerable to reflected XSS due to lack of filtration of user-supplied data in a search query. NOTE: It is asserted that an attacker must have the same access rights as the user in order to be able to execute…
- 5.4CVE-2019-13645EPSS 0.7%
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file names. The JavaScript code is executed during attachments/edit/$file_id$ attachment editing. NOTE: It is asserted that an…
- 5.4CVE-2019-13644EPSS 0.7%
Firefly III before 4.7.17.1 is vulnerable to stored XSS due to lack of filtration of user-supplied data in a budget name. The JavaScript code is contained in a transaction, and is executed on the tags/show/$tag_number$ tag summary page. NO…