Skip to main content
VulnerabilityPublished Updated

CVE-2024-22075: Firefly III · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium : upgrade to 6.1.1 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.1.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade firefly-iii/firefly-iii to 6.1.1.

Affected software

ProductAffectedFixed in
GitHubfirefly-iii/firefly-iiipkg:github/firefly-iii/firefly-iiiOther threatsAffected
  • <6.1.1
Fixed in
  • 6.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-22075, organizations should promptly upgrade Firefly III to version 6.1.1 or later once the patch is available. In the interim, administrators should restrict webhook usage to trusted sources and validate or sanitize all webhook inputs rigorously to prevent injection of malicious HTML content. Implement Content Security Policy (CSP) headers to limit the execution of injected scripts in browsers. Educate users about the risks of interacting with unsolicited webhook notifications or links. Monitor webhook endpoints for unusual or suspicious payloads. Employ web application firewalls (WAFs) with rules targeting XSS and HTML injection patterns. Review and harden authentication and session management mechanisms to reduce the impact of potential session hijacking. Conduct regular security assessments and code reviews focusing on input validation and output encoding in webhook-related components. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Description

Firefly III (aka firefly-iii) before 6.1.1 allows webhooks HTML Injection.

References

Community reviews

Loading reviews…