CVE-2025-6266
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was detected in Teledyne FLIR AX8 up to 1.46. Affected by this vulnerability is an unknown functionality of the file /upload.php. Performing manipulation of the argument File results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 1.49.16 addresses this issue. Upgrading the affected component is recommended. The vendor points out: "FLIR AX8 internal web site has been refactored to be able to handle the reported vulnerabilities."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnauthenticated unrestricted file upload vulnerability in Teledyne FLIR AX8 thermal camera firmware versions up to 1.46. The /upload.php endpoint accepts arbitrary file uploads without authentication or validation via the 'File' parameter, allowing remote attackers to upload malicious files (e.g., web shells) to the device. Fixed in version 1.49.16.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.49.16CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FLIR AX8 device on networkLocate the device by checking for HTTP/HTTPS responses from the device's web interface, typically on ports 80/443, or identify via network scan for vendor-specific HTTP headers or the /login.php page returning FLIR AX8 contentAffected if The device is a Teledyne FLIR AX8 thermal camera
-
Determine firmware versionAccess the device's web interface (typically http://<device-ip>/) and navigate to the System or About section to view the firmware version, or query the device's API/config for the version stringAffected if The firmware version is shown as below 1.49.16 (e.g., 1.46 or earlier)
-
Check if web interface is network-accessibleVerify that the device's HTTP port (80/443) is reachable from network segments outside the local management VLAN, or test access to http://<device-ip>/upload.php from an external positionAffected if The /upload.php endpoint is accessible from untrusted network segments without authentication
-
Verify upload.php endpoint responseSend a benign HTTP POST request to http://<device-ip>/upload.php with a simple test file (or check if the endpoint accepts requests without auth headers), and observe if the server accepts and processes the upload without returning authentication errorsAffected if The endpoint accepts unauthenticated file uploads and returns a successful response
You are affected if you have a FLIR AX8 device running firmware version below 1.49.16 with the web interface network-accessible, allowing unauthenticated access to the /upload.php endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.49.16
Upgrade FLIR AX8 firmware to version 1.49.16 or later. If immediate patching is not feasible, restrict network access to the device's web interface via firewall or VLAN segmentation to limit exposure.
1.49.16
- Obtain the official FLIR Ax8 firmware version 1.49.16 from Teledyne FLIR's official support website
- Access the FLIR Ax8 device through its web interface or administrative console
- Navigate to the firmware update section of the device management interface
- Upload the version 1.49.16 firmware file to the device
- Wait for the firmware upload and installation process to complete
- Restart the device if prompted or required by the update process
- Verify that the device is now running firmware version 1.49.16
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6266 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6266 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data