FlamingoApplication · Vitec

CVE-2026-61498

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to after 4.12.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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
Vitec Flamingo 4.12.2 contains an unauthenticated OS command injection vulnerability in the admin/ajax/gen_graphs.php endpoint that allows remote unauthenticated attackers to execute arbitrary commands by supplying shell metacharacters in the start, end, key, or format HTTP GET parameters. Attackers can exploit the lack of input sanitization in the graph generation script, which passes user-supplied values directly to shell commands via passthru(), to execute arbitrary OS commands with root privileges due to the web server context having passwordless sudo access.

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

Unauthenticated OS command injection in Vitec Flamingo 4.12.2 admin/ajax/gen_graphs.php endpoint. Attackers can inject arbitrary shell commands via unsanitized HTTP GET parameters (start, end, key, format) passed directly to passthru(), achieving root-level code execution due to passwordless sudo configuration.

MitigationImplement strict input validation/whitelisting on the gen_graphs.php endpoint to block shell metacharacters, and remove passwordless sudo privileges from the web server user context.

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
FlamingoApplication
Affected:<= 4.12.2

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. Identify Vitec Flamingo version
    Locate the installation directory and check version files (e.g., version.php, VERSION.txt, or admin/config.php) for the installed Flamingo version number
    Affected if installed version matches 4.12.2 exactly or is lower than 4.12.2
  2. Verify vulnerable endpoint exists
    Check for the presence of admin/ajax/gen_graphs.php in the web document root or application installation path
    Affected if the file admin/ajax/gen_graphs.php exists on the system
  3. Check sudo configuration for web server user
    Run 'sudo -l' as the web server user (www-data, apache, nginx) without a password to enumerate passwordless sudo rules
    Affected if the web server user has passwordless sudo privileges configured in /etc/sudoers or /etc/sudoers.d/
  4. Test parameter acceptance on gen_graphs.php
    Send a benign HTTP GET request to admin/ajax/gen_graphs.php with test values for start, end, key, and format parameters and observe if they are processed
    Affected if the endpoint accepts and processes these GET parameters without validation errors

User is affected if Vitec Flamingo version is 4.12.2 or lower, the gen_graphs.php endpoint exists, and the web server user has passwordless sudo privileges enabling root-level command execution through the injection point.

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.

From vendor data
Upgrade available Upgrade to a release after 4.12.2
Interim mitigation

Implement strict input validation/whitelisting on the gen_graphs.php endpoint to block shell metacharacters, and remove passwordless sudo privileges from the web server user context.

Fix this in Flamingo Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61498 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61498 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