CVE-2023-37289
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 · uneditedIt is identified a vulnerability of Unrestricted Upload of File with Dangerous Type in the file uploading function in InfoDoc Document On-line Submission and Approval System, which allows an unauthenticated remote attacker can exploit this vulnerability without logging system to upload and run arbitrary executable files to perform arbitrary system commands or disrupt service. This issue affects Document On-line Submission and Approval System: 22547, 22567.
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 confidenceA critical unrestricted file upload vulnerability exists in InfoDoc Document On-line Submission and Approval System (versions 22547, 22567). The file uploading function fails to validate uploaded file types, allowing unauthenticated remote attackers to upload executable files (e.g., .exe, .php, .jsp, .asp) and achieve arbitrary command execution on the underlying server. No authentication is required to exploit this flaw.
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= 22547= 22567CVSS 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.
-
Confirm InfoDoc system is runningIdentify the web application by checking the application banner, title, or HTTP headers for 'InfoDoc', 'Document On-line Submission', or related identifiers. Check the application's about/help page or login page for product version information.Affected if The product is InfoDoc Document On-line Submission and Approval System and the version is exactly 22547 or 22567.
-
Locate the file upload endpointSearch the application for file upload functionality: look for HTML forms with 'enctype=multipart/form-data', input elements with type='file', or URLs containing '/upload', '/submit', '/documents/upload', or similar paths. These may be on submission or approval pages.Affected if A file upload form or API endpoint exists and is accessible without authentication.
-
Test unrestricted file uploadUsing a tool like Burp Suite or curl, send a POST request to the upload endpoint with an executable file extension (.php, .jsp, .asp, .exe) in the filename field, without providing any authentication cookies or tokens. Observe if the server accepts the file and returns a success response.Affected if The server accepts and stores files with executable extensions (.php, .jsp, .asp, .exe) without rejecting them or requiring authentication.
-
Verify uploaded file is accessibleIf the upload returns a success response, check if the uploaded file is accessible via a direct URL (e.g., /uploads/filename.php). Attempt to access the file in a browser or via curl to confirm it was stored in the web root and is executable.Affected if Uploaded executable files are stored in a location accessible via the web server and can be executed.
You are affected if you run InfoDoc Document On-line Submission and Approval System version 22547 or 22567 and the file upload functionality accepts executable file types without authentication.
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 dataImmediately restrict the file upload function to accept only whitelisted non-executable file types (e.g., PDF, DOC, DOCX, TXT), implement server-side validation of file magic bytes/mime types (not just extensions), store uploaded files outside the web root with random filenames, and require authentication for all upload operations.
- Consultation6.0 h
- Implementation16.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37289 — 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-2023-37289 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