dbcve.org
OmflowApplication · Syscomgo

CVE-2024-8779

HIGH · 8.8 CVSS v3.1 Published 2024-09-16
Fix available
A fix is available. Upgrade to 1.2.1.3 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
OMFLOW from The SYSCOM Group does not properly restrict access to the system settings modification functionality, allowing remote attackers with regular privileges to update system settings or create accounts with administrator privileges, thereby gaining control of the server.

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

Broken access control vulnerability in OMFLOW allows authenticated regular users to modify system settings or create administrator accounts due to missing or insufficient authorization checks on administrative functions.

MitigationImplement proper role-based access control (RBAC) to ensure system settings modification and account creation functions are restricted to users with administrator privileges only.

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
OmflowApplication
Affected:>= 1.1.6.0, < 1.2.1.3

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 the installed Syscomgo Omflow version
    Locate and read the version information for your Syscomgo Omflow installation, typically found in the product about page, installation directory, or system information panel
    Affected if The installed version is 1.1.6.0 or higher but lower than 1.2.1.3
  2. Determine if user authentication is enabled
    Verify whether the Omflow system is configured to require user login for access, typically through authentication settings or login configuration
    Affected if User authentication is required and regular (non-administrator) accounts exist in the system
  3. Verify regular user account existence
    Check if there are any non-administrator user accounts configured in the Omflow system
    Affected if At least one regular (non-admin) user account exists in the system
  4. Inspect administrative function access controls
    Review the user role permissions and access control configurations to determine whether regular users can access administrative functions such as system settings modification or account creation
    Affected if Regular users have permission to access administrative functions or account creation features

Your environment is affected if you are running Syscomgo Omflow version 1.1.6.0 through 1.2.1.2 and regular authenticated users can access administrative functions or create accounts.

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 1.2.1.3 or later
Fixed in 1.2.1.3
Interim mitigation

Implement proper role-based access control (RBAC) to ensure system settings modification and account creation functions are restricted to users with administrator privileges only.

Recommended fix High confidence

Omflow 1.2.1.3 or later

  1. Identify current Omflow version by checking the application or system information
  2. Download Omflow version 1.2.1.3 or later from the official vendor (The SYSCOM Group)
  3. Create a full backup of the current Omflow installation including database and configuration files
  4. Test the upgrade in a staging environment before applying to production
  5. Apply the upgrade following vendor-provided installation instructions
  6. Verify the upgrade was successful by checking the new version number
  7. Confirm that the access control vulnerability is remediated by testing that regular users can no longer modify system settings or create administrator accounts

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

Fix this in Omflow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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