dbcve.org
Openvpn Cms FlaskApplication · Xiaoyunjie

CVE-2025-6775

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-27
Fix available
A fix is available. Upgrade to 1.2.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 classified as critical has been found in xiaoyunjie openvpn-cms-flask up to 1.2.7. This affects the function create_user of the file /app/api/v1/openvpn.py of the component User Creation Endpoint. The manipulation of the argument Username leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.2.8 is able to address this issue. The patch is named e23559b98c8ea2957f09978c29f4e512ba789eb6. It is recommended to upgrade the affected component.

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 command injection vulnerability exists in the openvpn-cms-flask User Creation Endpoint (create_user function in /app/api/v1/openvpn.py). The Username parameter is not properly sanitized before being passed to a system command, allowing remote attackers to execute arbitrary OS commands via crafted username input.

MitigationUpgrade openvpn-cms-flask to version 1.2.8 or later to obtain the patch that properly sanitizes user input in the create_user function.

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
Openvpn Cms FlaskApplication
Affected:< 1.2.8

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 if openvpn-cms-flask is running
    Check running processes for 'openvpn-cms-flask' or 'flask' related to openvpn. Look for process listings using 'ps aux | grep -i openvpn' or 'ps aux | grep -i flask'
    Affected if The application process is running and exposes the vulnerable endpoint
  2. Locate the application installation
    Search for the openvpn-cms-flask application directory. Common paths include /app, /opt, or the user's home directory. Look for directories containing 'openvpn' and 'cms' in the name.
    Affected if The application directory exists and contains the vulnerable code file /app/api/v1/openvpn.py
  3. Determine installed version
    Check for version information in the application. Look for version files, setup.py, requirements.txt, or check the Git repository tags if accessible. Search for version strings like 'version' or '__version__' in Python files.
    Affected if The installed version is lower than 1.2.8 (e.g., 1.2.7, 1.2.6, etc.)
  4. Verify vulnerable code exists
    Inspect the file /app/api/v1/openvpn.py and locate the create_user function. Look for system command execution (os.system, subprocess, shell=True) that incorporates the Username parameter without proper sanitization.
    Affected if The create_user function contains unsanitized command execution using the Username parameter

You are affected if the openvpn-cms-flask application is running with a version lower than 1.2.8 and the vulnerable create_user function in /app/api/v1/openvpn.py uses the Username parameter in an unsafe system command.

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.8 or later
Fixed in 1.2.8
Vendor patch github.com →
Interim mitigation

Upgrade openvpn-cms-flask to version 1.2.8 or later to obtain the patch that properly sanitizes user input in the create_user function.

Recommended fix High confidence

1.2.8

  1. Check the current installed version of openvpn-cms-flask by running: pip show openvpn-cms-flask or checking your requirements.txt
  2. Upgrade to version 1.2.8 using pip: pip install openvpn-cms-flask==1.2.8
  3. If using a Git installation, pull the latest code from the repository and ensure you have commit e23559b98c8ea2957f09978c29f4e512ba789eb6 or later
  4. Restart the application service to load the updated code
  5. Verify the upgrade was successful by checking the version again

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

Fix this in Openvpn Cms Flask Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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