Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii


Reported on

Aug 20th 2021

✍️ Description

Attacker able to set default currency with CSRF attack.

It does not matter at all that your application run in localhost or elsewhere, just it is enough to run on a browser and another low privilege user or attackers know the IP address or hostname of your application.

In CSRF attacks it is necessary that a user logged into your application and just going to a malicious website and after that only with a redirection attacker can perform attack on unprotected endpoint, this means only with visiting a site a unwanted action will be perform without that user aware from that.

🕵️‍♂️ Proof of Concept

1.fisrt admin already should be logged in Browser.

2.Open the PoC.html (it is auto-submit).

3.Here a set default currency with id 22 will be set to default after the PoC.html file opened.

// PoC.html

  <script>history.pushState('', '', '/')</script>
    <form action="">
      <input type="submit" value="Submit request" />

This PoC can perform attack without that users noticed and Also PoC can send multiple request at same time that means attacker can Bruteforce all possible actions ( with using multiple Iframe )

💥 Impact

This vulnerability is capable of change default currency.


The easiest way that you set strict attribute on each cookie, Or you set Lax and Use GET requests only for receiving data not changing them.

The best way is that you set a CSRF token in each endpoint.


We have contacted a member of the firefly-iii team and are waiting to hear back 2 years ago
James Cole validated this vulnerability 2 years ago
amammad has been awarded the disclosure bounty
The fix bounty is now up for grabs
James Cole
2 years ago

Nice, also fixed. Should also be up on the demo site. Fix will be part of the normal release cycle.

James Cole marked this as fixed with commit 06d319 2 years ago
James Cole has been awarded the fix bounty
This vulnerability will not receive a CVE
2 years ago


this is OK now.

nice and quick fix.

Jamie Slome
2 years ago


CVE published! It should be made publically available via MITRE/NVD shortly.

2 years ago


@admin awesome, thanks.

to join this conversation