LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13644: Firefly III before 4.7.17.1 is vulnerable to stored XSS due to lack of filtration of user-supplied data in...

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

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Firefly III versions before 4.7.17.1 can store unsafe JavaScript in a budget name. When a user later views the affected tag summary page, that script may run in their browser. Business impact is mainly account-context data exposure or unauthorized UI actions, limited by required application access.

Executive priority

Treat this as a moderate-priority application hygiene fix. It is unlikely to drive emergency response by itself, but finance-tracking data and authenticated user sessions are sensitive enough to justify prompt upgrade and access review.

Technical view

This is stored XSS in Firefly III budget-name handling. The CVE says unfiltered user-supplied budget data can be contained in a transaction and execute on tags/show/$tag_number$. CVSS 3.1 is 5.4: network reachable, low complexity, low privilege required, user interaction required, changed scope, low confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to Firefly III deployments running versions before 4.7.17.1. Risk is higher where multiple users have rights to create or modify budgets, transactions, or tag-related records. The source bundle does not provide CPEs or broader affected-product metadata.

Exploitation context

The CVE is not marked KEV, and the provided sources do not state active exploitation. The record notes an attacker must have the same access rights as the user to execute the vulnerability, so this is not described as unauthenticated compromise.

Researcher notes

Key constraints are important: stored XSS, authenticated or same-rights attacker, user interaction required, and no provided evidence of exploitation in the wild. The vulnerable sink is the tag summary page, with tainted budget-name data carried through transaction context.

Mitigation direction

  • Upgrade Firefly III to 4.7.17.1 or later.
  • Restrict budget and transaction editing to trusted users until upgraded.
  • Review vendor issue and comparison references for the exact fix context.
  • Audit existing budget names and related transactions for suspicious stored content.

Validation and detection

  • Inventory Firefly III versions and flag anything before 4.7.17.1.
  • Confirm tag summary pages render budget names safely after remediation.
  • Check whether untrusted users can create or edit budget-related records.
  • Review logs or records for unexpected script-like content in budget names.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13644 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2019-13644Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.