dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-11906

MEDIUM · 6.7 CVSS v3.1 Published 2025-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 versions prior 12.5.6 where certain system configuration files have incorrect file permissions, allowing a user with access to the default flowmon system user account used for SSH access to potentially escalate privileges to root during service initialization.

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 privilege escalation vulnerability in Progress Flowmon versions before 12.5.6 allows users with SSH access to the default flowmon system account to modify system configuration files that have incorrect (overly permissive) file permissions. During service initialization, these files are read and executed with root privileges, enabling the attacker to gain root access.

MitigationUpgrade to Flowmon version 12.5.6 or later which contains the corrected file permissions. As a compensating control, audit and restrict permissions on system configuration files to follow least-privilege principles.

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

CVSS:3.1/AV:L/AC:L/PR:H/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 installation and version
    Run 'rpm -qa | grep -i flowmon' or 'dpkg -l | grep -i flowmon' to find installed Flowmon packages, then check the version against the affected range (versions before 12.5.6). If using a web interface, log in and navigate to Help > About to view the version.
    Affected if Flowmon version is present and is lower than 12.5.6
  2. Verify flowmon system account exists
    Check for the 'flowmon' user account by running 'id flowmon' or looking in /etc/passwd with 'grep flowmon /etc/passwd'. Confirm SSH access is permitted by reviewing /etc/ssh/sshd_config for AllowUsers or AllowGroups containing flowmon.
    Affected if A 'flowmon' user account exists and is allowed SSH access
  3. Identify configuration files with permissive ownership
    Search for configuration files in common Flowmon directories (typically under /opt/flowmon, /etc/flowmon, or /var/opt/flowmon) that are owned by the flowmon user or group, or have world-writable permissions (permissions ending in 'o+w' or '777'). Use 'find /opt/flowmon -user flowmon -o -group flowmon -o -perm -002 2>/dev/null' as a starting point.
    Affected if Configuration files are owned by or writable by the flowmon user account
  4. Check if root-owned processes read flowmon-writable files
    Review the Flowmon service configuration (systemd service file or init script) to identify which processes run as root. Examine the service startup scripts to determine which configuration files they read during initialization. Cross-reference that these files are writable by the flowmon user.
    Affected if A root-owned service process reads and executes configuration files that the flowmon user can modify

You are affected if Flowmon version is below 12.5.6, a flowmon user account with SSH access exists, and configuration files writable by that user are read by root-owned services during initialization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Flowmon version 12.5.6 or later which contains the corrected file permissions. As a compensating control, audit and restrict permissions on system configuration files to follow least-privilege principles.

Recommended fix High confidence

12.5.6

  1. Back up all Flowmon configuration files and databases before upgrading
  2. Upgrade Progress Flowmon to version 12.5.6 or later
  3. After upgrade, verify that system configuration files have correct permissions (should not be world-writable or group-writable by the flowmon user)
  4. Restart the Flowmon services and verify normal operation
  5. Confirm the flowmon user cannot escalate to root via the previously vulnerable file permissions

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

Have this fixed 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 help mitigating

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-2025-11906 — 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-11906 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