CVE-2025-7576
BaseFortify
Publication date: 2025-07-14
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| teledyne_flir | fh-series_id | 1.3.2.16 |
| teledyne_flir | fb-series_o | 1.3.2.16 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-266 | A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. |
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7576 is an improper access control vulnerability in Teledyne FLIR FB-Series O and FLIR FH-Series ID firmware version 1.3.2.16. It affects a management backend file named 'production.html' located in a private directory. Due to a server misconfiguration, this file is publicly accessible over the network without authentication, allowing attackers to bypass access restrictions remotely. This can lead to unauthorized access, information disclosure, and potentially remote code execution. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized remote access to sensitive management interfaces, disclosure of confidential information, and potentially remote code execution on the affected device. This compromises the confidentiality, integrity, and availability of the system, posing a high risk to users relying on the affected Teledyne FLIR products. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the exposed management backend file accessible over the network without authentication. You can use network scanning or web request tools to look for the URL path '/priv/production/production.html' on your devices. A suggested command is to use curl or wget to request the URL and see if it is accessible without authentication, for example: curl http://<target-ip>/priv/production/production.html. Additionally, Google Dorking with the query 'inurl:priv/production/production.html' can help locate vulnerable targets externally. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling public access to the '/priv/production/production.html' file or the management backend entirely, as it is intended for internal use only. Since no official mitigations or patches have been published and the vendor has not responded, it is recommended to replace the affected product with an alternative that does not have this vulnerability. Network-level controls such as firewall rules to block external access to this path can also help reduce exposure. [2]