CVE-2022-31563
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 whmacmac/vprj repository through 2022-04-06 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.
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 confidenceA path traversal vulnerability exists in the whmacmac/vprj Flask application where the send_file function is called with unsanitized user input. This allows attackers to access arbitrary files on the server by manipulating path parameters, potentially exposing sensitive system files, configuration files, or application source code.
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<= 2022-04-06CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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 Vprj Project Vprj installation and versionLocate the whmacmac/vprj application codebase or package. Check the version by examining version files, setup.py, requirements.txt, git tags, or the application metadata. Compare the installed version against the affected range: <= 2022-04-06Affected if The installed version is 2022-04-06 or earlier
-
Locate send_file calls in the Flask applicationSearch the application source code for uses of Flask's send_file function. Look in all Python files (*.py) for patterns like 'send_file(' or 'from flask import send_file'. Identify the endpoints or routes that invoke this function.Affected if The application code contains send_file calls that handle file serving
-
Inspect send_file argument handlingExamine each send_file call found. Determine whether the argument passed to send_file is derived from user input (request parameters, URL paths, form data, query strings). Search for patterns such as send_file(request.args.get(...)), send_file(path), or similar where path comes directly from user requests without intermediate processing.Affected if User-supplied input flows directly to send_file without transformation
-
Verify absence of input sanitizationReview the code between user input and send_file calls. Look for the use of Flask's safe_join, os.path.realpath, or path validation logic that verifies the resolved path stays within an allowed directory. Check if any sanitization or validation functions are called on the path before send_file is invoked.Affected if No sanitization functions (safe_join, path validation) are present between user input and send_file
-
Determine application exposureCheck if the Flask application is running and accessible over a network. Identify the binding address (0.0.0.0 vs localhost), firewall rules, and whether the vulnerable endpoints are exposed to untrusted users or the internet.Affected if The application is network-accessible and vulnerable send_file endpoints are exposed to untrusted users
You are affected if the installed Vprj version is 2022-04-06 or earlier AND the application uses send_file with direct user input without sanitization via safe_join or equivalent path validation.
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 dataSanitize and validate all path inputs before passing them to Flask's send_file function. Use secure path-joining methods (e.g., Flask's safe_join) and verify the resolved path remains within the intended directory to prevent directory traversal attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31563 — 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-31563 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