dbcve.org
Flir Ax8 FirmwareOperating system · Flir

CVE-2023-51126

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to after 1.46.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Command injection vulnerability in /usr/www/res.php in FLIR AX8 up to 1.46.16 allows attackers to run arbitrary commands via the value parameter. NOTE: The vendor has stated that with the introduction of firmware version 1.49.16 (Jan 2023) the FLIR AX8 should no longer be affected by the vulnerability reported. Latest firmware version (as of Oct 2025, was released Jun 2024) is 1.55.16.

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 confidence

A command injection vulnerability exists in the /usr/www/res.php script of FLIR AX8 thermal imaging cameras. Attackers can inject and execute arbitrary operating system commands through the 'value' parameter. The vulnerability affects firmware versions up to 1.46.16 and was patched in firmware version 1.49.16 released January 2023.

MitigationUpgrade FLIR AX8 firmware to version 1.49.16 or later (current latest is 1.55.16). If immediate patching is not possible, network segmentation and restricting web interface access should be implemented to reduce attack surface.

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
Flir Ax8 FirmwareOperating system
Affected:<= 1.46.16

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check FLIR AX8 firmware version
    Access the camera's web interface and navigate to the System or About page, or use the FLIR AX8 management interface to view firmware version information. Alternatively, check via SNMP or the camera's API if available.
    Affected if The firmware version displayed is 1.46.16 or lower, or any version below 1.49.16.
  2. Verify web interface accessibility
    Attempt to access the camera's web interface by navigating to the device's IP address in a web browser. Check if port 80 or 443 is open and responding.
    Affected if The web interface is exposed and accessible from network segments where untrusted users could reach it.
  3. Confirm vulnerable script presence
    Check if the /usr/www/res.php script exists on the device by attempting to access it via HTTP (e.g., http://<device-ip>/res.php) or by reviewing firmware filesystem if firmware can be extracted.
    Affected if The res.php script is present and the 'value' parameter accepts user input without sanitization.
  4. Identify exposure to network
    Review firewall rules, ACLs, or network segmentation configurations to determine if the camera's web interface (port 80/443) is reachable from untrusted networks or the internet.
    Affected if The device web interface is reachable from untrusted network segments or directly from the internet without proper access controls.

You are affected if your FLIR AX8 firmware is version 1.46.16 or lower (below 1.49.16) and the web interface with the vulnerable /usr/www/res.php script is accessible from your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.46.16
Interim mitigation

Upgrade FLIR AX8 firmware to version 1.49.16 or later (current latest is 1.55.16). If immediate patching is not possible, network segmentation and restricting web interface access should be implemented to reduce attack surface.

Recommended fix High confidence

FLIR Ax8 Firmware 1.55.16 (minimum fixed: 1.49.16)

  1. 1. Access the FLIR Ax8 device administration interface
  2. 2. Navigate to the firmware update section in settings
  3. 3. Download the latest firmware version 1.55.16 from the official FLIR support website
  4. 4. Upload and apply the firmware update to the device
  5. 5. After reboot, verify the device is running firmware version 1.49.16 or higher
  6. 6. Confirm the vulnerability is remediated by testing that the /res.php endpoint no longer accepts command injection via the value parameter

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flir Ax8 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51126 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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