CVE-2025-7578
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 found in Teledyne FLIR FB-Series O and FLIR FH-Series ID 1.3.2.16. It has been declared as critical. This vulnerability affects the function sendCommand of the file runcmd.sh. The manipulation of the argument cmd leads to command injection. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The researcher highlights, that "[a]lthough this functionality is currently disabled due to server CGI configuration errors, it is essentially a 'time bomb' waiting to be activated". The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceCommand injection vulnerability in the sendCommand function of runcmd.sh in Teledyne FLIR FB-Series O and FH-Series ID cameras (version 1.3.2.16). The 'cmd' argument is not properly sanitized before being passed to shell execution, allowing remote attackers to inject arbitrary shell commands. While currently disabled due to CGI misconfiguration, the vulnerable code remains present as a latent risk.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
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 camera modelAccess the camera web interface or check the device label to confirm the model is Teledyne FLIR FB-Series O or FH-Series IDAffected if Camera model is FB-Series O or FH-Series ID
-
Check firmware versionNavigate to the camera's web interface System or About page, or use the API endpoint that exposes firmware version information, and verify the installed version matches 1.3.2.16Affected if Firmware version is 1.3.2.16
-
Verify CGI interface accessibilityAttempt to access the CGI endpoint for sendCommand (e.g.,/cgi-bin/runcmd.sh?cmd=) either through direct HTTP request or by checking the web server configurationAffected if CGI interface is accessible and the vulnerable endpoint responds to requests
-
Locate vulnerable scriptCheck the camera filesystem for the presence of runcmd.sh in the /cgi-bin/ or equivalent directory where CGI scripts are storedAffected if The runcmd.sh script exists on the device
-
Confirm sendCommand function is enabledSend a test request to the sendCommand function endpoint (e.g., /cgi-bin/runcmd.sh?cmd=test) and verify it executes or returns a response indicating the function is activeAffected if The sendCommand function responds and appears to process the cmd parameter
You are affected if you have a Teledyne FLIR FB-Series O or FH-Series ID camera running firmware version 1.3.2.16 where the CGI interface is accessible and the sendCommand function in runcmd.sh is enabled.
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.
From vendor dataRestrict access to the CGI interface, implement proper input validation/sanitization on the cmd parameter, and disable or remove the vulnerable sendCommand function if not required. Consider network segmentation for these camera devices.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-7578 — 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-7578 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