Vulnerabilities (CVE)

Filtered by vendor Firefly-iii Subscribe
Filtered by product Firefly Iii
Total 26 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
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