CVE-2019-14671 is a low-severity (CVSS 3.3) Improper Input Validation vulnerability in grumpydictator/firefly-iii. 1 public exploit reference exists, so weaponization risk is real. A fix is available for grumpydictator/firefly-iii — see the affected versions and patch details below.
Improper Input Validation in Firefly III
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2019-14671 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
grumpydictator/firefly-iiiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | grumpydictator/firefly-iii | all versions | 4.7.17.4composer require grumpydictator/firefly-iii:^4.7.17.4 |
Affected Products
firefly iiifirefly-iiiResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grumpydictator/firefly-iii, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update grumpydictator/firefly-iii to 4.7.17.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14671 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2019-14671 in your dependencies?
Find it across Packagist, including transitive dependencies.