Total
26 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2024-22075 | 1 Firefly-iii | 1 Firefly Iii | 2025-06-05 | N/A | 6.1 MEDIUM |
|
Firefly III (aka firefly-iii) before 6.1.1 allows webhooks HTML Injection.
|
|||||
| CVE-2023-1789 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | N/A | 9.8 CRITICAL |
|
Improper Input Validation in GitHub repository firefly-iii/firefly-iii prior to 6.0.0.
|
|||||
| CVE-2023-1788 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | N/A | 9.8 CRITICAL |
|
Insufficient Session Expiration in GitHub repository firefly-iii/firefly-iii prior to 6.
|
|||||
| CVE-2023-0298 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | N/A | 6.5 MEDIUM |
|
Incorrect Authorization in GitHub repository firefly-iii/firefly-iii prior to 5.8.0.
|
|||||
| CVE-2021-4015 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 4.3 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-4005 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 4.3 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3921 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 4.3 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3901 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 6.8 MEDIUM | 8.8 HIGH |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3900 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 6.5 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3851 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.9 MEDIUM | 5.4 MEDIUM |
|
firefly-iii is vulnerable to URL Redirection to Untrusted Site
|
|||||
| CVE-2021-3846 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 6.5 MEDIUM | 8.8 HIGH |
|
firefly-iii is vulnerable to Unrestricted Upload of File with Dangerous Type
|
|||||
| CVE-2021-3819 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 6.8 MEDIUM | 8.8 HIGH |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3730 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 6.5 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3729 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 4.3 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3728 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 6.5 MEDIUM |
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
|||||
| CVE-2021-3663 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
|
firefly-iii is vulnerable to Improper Restriction of Excessive Authentication Attempts
|
|||||
| CVE-2019-14672 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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.
|
|||||
| CVE-2019-14671 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 2.1 LOW | 3.3 LOW |
|
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 import/create/fints.
|
|||||
| CVE-2019-14670 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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.
|
|||||
| CVE-2019-14669 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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.
|
|||||
| CVE-2019-14668 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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.
|
|||||
| CVE-2019-14667 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 4.3 MEDIUM | 6.1 MEDIUM |
|
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 transaction action.
|
|||||
| CVE-2019-13647 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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 an attacker must have the same access rights as the user in order to be able to execute the vulnerability
|
|||||
| CVE-2019-13646 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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 the vulnerability
|
|||||
| CVE-2019-13645 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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 attacker must have the same access rights as the user in order to be able to execute the vulnerability
|
|||||
| CVE-2019-13644 | 1 Firefly-iii | 1 Firefly Iii | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
|
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. NOTE: It is asserted that an attacker must have the same access rights as the user in order to be able to execute the vulnerability
|
|||||