CVE-2022-39036
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 · uneditedThe file upload function of Agentflow BPM has insufficient filtering for special characters in URLs. An unauthenticated remote attacker can exploit this vulnerability to upload arbitrary file and execute arbitrary code to manipulate system or disrupt service.
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 confidenceAgentflow BPM contains a file upload function with insufficient filtering for special characters in URLs, allowing unauthenticated remote attackers to bypass authentication and upload malicious files. The lack of proper input sanitization on filename/path parameters enables path traversal and arbitrary file placement, leading to remote code execution.
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= 4.0.0.1183.552CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Agentflow BPM installationLocate the Agentflow BPM installation directory or check running services for 'Agentflow', 'flowring', or 'bpm' processes on the system. Check for web applications serving Agentflow content (typically on port 8080 or 8443).Affected if The product Flowring Agentflow BPM is installed and running on the system.
-
Check installed versionLocate version information in the installation - typically in a version file, about page, or manifest within the Agentflow installation directory. Common paths include WEB-INF/version.properties, version.txt, or the application banner/logs.Affected if The installed version is exactly 4.0.0.1183.552.
-
Verify file upload endpoint accessibilityIdentify and access the web-based file upload functionality in Agentflow BPM. Look for upload endpoints in the web interface, typically under paths like /upload, /file/upload, /attachment/upload, or within workflow/form modules.Affected if The file upload web interface is accessible without authentication or with the configured authentication method.
-
Check for unauthenticated access possibilityAttempt to access the file upload endpoint without providing credentials, or with invalid credentials. Examine whether the application allows anonymous access to upload-related URLs or if authentication can be bypassed.Affected if Unauthenticated access to the file upload function is possible, or authentication can be bypassed.
The environment is affected if Flowring Agentflow version 4.0.0.1183.552 is installed AND the file upload web interface is accessible, allowing unauthenticated or bypassed access for path traversal-based file uploads.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict allowlist-based validation for filenames and paths, sanitize special characters, enforce file type restrictions via magic byte detection, store uploads outside web root, and add proper authentication/authorization checks.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39036 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39036 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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