dbcve.org
Flowmon Anomaly Detection SystemApplication · Progress

CVE-2025-13774

HIGH · 8.8 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to after 13.0.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability exists in Progress Flowmon ADS versions prior to 12.5.4 and 13.0.1 where an SQL injection vulnerability allows authenticated users to execute unintended SQL queries and commands.

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 · moderate confidence

SQL injection vulnerability in Progress Flowmon ADS allows authenticated users to execute arbitrary SQL commands by injecting malicious SQL statements through vulnerable input parameters, potentially leading to unauthorized data access or database compromise.

MitigationUpdate Flowmon ADS to version 12.5.4 or 13.0.1 or later. If immediate patching is not possible, review and restrict user privileges and sanitize all user-supplied input in application queries.

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
Flowmon Anomaly Detection SystemApplication
Affected:>= 12.0.0, <= 12.5.4>= 13.0.0, <= 13.0.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Flowmon ADS installation
    Locate the Flowmon ADS application on the system - typical installation paths include /opt/flowmon/ or check for flowmon services running (service flowmon-ads status or systemctl status flowmon-ads)
    Affected if Flowmon ADS is installed and running on the system
  2. Determine installed version
    Check the installed version through the web UI (typically at /about or /help), CLI (flowmon-ads --version), or package manager (rpm -qa | grep flowmon or dpkg -l | grep flowmon)
    Affected if The version falls within 12.0.0 to 12.5.4 or 13.0.0 to 13.0.1
  3. Verify remote access is enabled
    Check if the web interface or API is accessible remotely (look for binding to non-localhost interfaces in configuration files, typically in /etc/flowmon/ or /opt/flowmon/config/)
    Affected if Remote access to the Flowmon ADS web interface or API is enabled, allowing external attackers to potentially obtain valid credentials
  4. Confirm authentication is in use
    Review authentication settings in the Flowmon ADS configuration to confirm user accounts exist and the login page is active
    Affected if User authentication is configured, as valid credentials are required to exploit this SQL injection vulnerability

A user is affected if Flowmon ADS version is 12.0.0 through 12.5.4 or 13.0.0 through 13.0.1 AND remote access with valid user accounts is available.

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 13.0.1
Interim mitigation

Update Flowmon ADS to version 12.5.4 or 13.0.1 or later. If immediate patching is not possible, review and restrict user privileges and sanitize all user-supplied input in application queries.

Recommended fix High confidence

Flowmon ADS 12.5.4 (for 12.x branch) or 13.0.1 or later (for 13.x branch)

  1. Identify the currently installed Flowmon ADS version in the web interface (Settings > System > About) or via CLI
  2. Determine which version branch you are on (12.x or 13.x) to select the appropriate upgrade path
  3. Review the release notes for Flowmon ADS 12.5.4 or 13.0.1 (whichever applies) for any migration requirements or known issues
  4. Create a full backup of the Flowmon ADS configuration and database before upgrading
  5. Download the appropriate upgrade package from the Progress Customer Portal or official distribution channel
  6. Follow the standard Flowmon upgrade procedure: stop services, run the upgrade installer, verify database migrations complete successfully
  7. Restart Flowmon services and verify the web interface is accessible
  8. Confirm the version number reflects the upgrade target (12.5.4 or 13.0.1)
Caveat No specific breaking changes documented in the provided description; standard upgrade precautions apply

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

Fix this in Flowmon Anomaly Detection System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13774 — 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-2025-13774 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