Vulnerability database
Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.
14 results
Aug 5, 2026Firefly III's webhook URL validator (IsValidWebhookUrl.php) filters most private/reserved IPv4 ranges but contains an explicit early-return that allows any resoCVE-2026-71250 · Other software · firefly-iii · reported by 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2cMedium 4.3
Firefly III's webhook URL validator (IsValidWebhookUrl.php) filters most private/reserved IPv4 ranges but contains an explicit early-return that allows any resolved address in 127.0.0.0/8, permitting an authenticated user (with webhooks enabled, which is off by default) to configure a webhook targeting loopback services on the server.
- Product
- firefly-iii
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 15, 2026Incorrect access control in the webhook management component of Project Firefly III v6.5.9 allows attackers to scan internal resources via a crafted POST requesCVE-2026-50886 · Other software · reported by MITRECritical 9.1
Incorrect access control in the webhook management component of Project Firefly III v6.5.9 allows attackers to scan internal resources via a crafted POST request.
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordgist.github.comgist.github.com
Jun 17, 2024Firefly III is a free and open source personal finance manager.CVE-2024-37893 · Other software · firefly-iii · reported by GitHubMedium 5.9
Firefly III is a free and open source personal finance manager. In affected versions an MFA bypass in the Firefly III OAuth flow may allow malicious users to bypass the MFA-check. This allows malicious users to use password spraying to gain access to Firefly III data using passwords stolen from other sources. As OAuth applications are easily enumerable using an incrementing id, an attacker could try sign an OAuth application up to a users profile quite easily if they have created one. The attacker would also need to know the victims username and password. This problem has been patched in Firefly III v6.1.17 and up. Users are advised to upgrade. Users unable to upgrade should Use a unique password for their Firefly III instance and store their password securely, i.e. in a password manager.
- Product
- firefly-iii
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 4, 2024Firefly III (aka firefly-iii) before 6.1.1 allows webhooks HTML Injection.CVE-2024-22075 · Other software · Firefly-iii · reported by MITREMedium 6.1
Firefly III (aka firefly-iii) before 6.1.1 allows webhooks HTML Injection.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordgithub.comsonarsource.com
Aug 5, 2019Firefly III 4.7.17.5 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the liability name field.CVE-2019-14672 · Other software · Firefly-iii · reported by MITREMedium 5.4
Firefly III 4.7.17.5 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the liability name field. The JavaScript code is executed upon an error condition during a visit to the account show page.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 5, 2019Firefly III 4.7.17.3 is vulnerable to local file enumeration.CVE-2019-14671 · Other software · Firefly-iii · reported by MITRELow 3.3
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.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 5, 2019Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the bill name field.CVE-2019-14670 · Other software · Firefly-iii · reported by MITREMedium 5.4
Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the bill name field. The JavaScript code is executed during rule-from-bill creation.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 5, 2019Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the asset account name.CVE-2019-14669 · Other software · Firefly-iii · reported by MITREMedium 5.4
Firefly III 4.7.17.3 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the asset account name. The JavaScript code is executed during a visit to the audit account statistics page.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 5, 2019Firefly 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.CVE-2019-14668 · Other software · Firefly-iii · reported by MITREMedium 5.4
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.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 5, 2019Firefly 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 thCVE-2019-14667 · Other software · Firefly-iii · reported by MITREMedium 6.1
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.
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 17, 2019Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file content.CVE-2019-13647 · Other software · Firefly-iii · reported by MITREMedium 5.4
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
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 17, 2019Firefly III before 4.7.17.3 is vulnerable to reflected XSS due to lack of filtration of user-supplied data in a search query.CVE-2019-13646 · Other software · Firefly-iii · reported by MITREMedium 5.4
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
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 17, 2019Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file names.CVE-2019-13645 · Other software · Firefly-iii · reported by MITREMedium 5.4
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
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 17, 2019Firefly III before 4.7.17.1 is vulnerable to stored XSS due to lack of filtration of user-supplied data in a budget name.CVE-2019-13644 · Other software · Firefly-iii · reported by MITREMedium 5.4
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
- Product
- Firefly III
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.