CVE-2025-10239 Unintended command execution via troubleshooting scripts in Progress Flowmon
High 7.2
Published
Updated
Check this codebase for CVE-2025-10239 and fix it if it is affected.
What it is: CVE-2025-10239 is a high-severity vulnerability in Progress Software Flowmon, published on 9 Oct 2025.
Exploitation: There is no known exploitation of CVE-2025-10239 in the wild and no public exploit code.
Affected product: Progress Software Flowmon. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-10239/ (Markdown: https://insights.sbomify.com/CVE-2025-10239/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-10239?
CVE-2025-10239 is a high-severity vulnerability in Progress Software Flowmon, published on 9 Oct 2025.
Official description
In Flowmon versions prior to 12.5.5, a vulnerability has been identified that allows a user with administrator privileges and access to the management interface to execute additional unintended commands within scripts intended for troubleshooting purposes.
Weakness: CWE-78
Which versions are affected by CVE-2025-10239?
How do I fix CVE-2025-10239?
No fix has been published for CVE-2025-10239 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-10239 being exploited?
There is no known exploitation of CVE-2025-10239 in the wild and no public exploit code.
Sources
Also known as GHSA-rv8j-66vg-2qg5.