dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-6211

HIGH · 8.7 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable

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
Unrestricted upload of file with dangerous type vulnerability in Global IT Informatics Services Inc. WEOLL allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects WEOLL: from 2.0.9 before 3.2.45.33.

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 confidence

Unrestricted file upload vulnerability in WEOLL allows attackers to upload dangerous file types (potentially executable files like .php, .jsp) without proper validation. Combined with ACL constraints not properly enforced, this can lead to remote code execution by accessing the uploaded files through the web server.

MitigationUpgrade to WEOLL version 3.2.45.33 or later. Additionally, implement server-side file type validation using allowlists, store uploads outside the web root, and enforce proper ACL controls on uploaded files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

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 WEOLL installation and version
    Locate the WEOLL installation directory and check the version file or binary. Common locations include /opt/weoll, the application root directory, or check the software's 'about' or 'version' information in the admin interface if accessible.
    Affected if The installed version is 2.0.9 or any version from 2.0.9 up to but not including 3.2.45.33
  2. Verify file upload functionality is enabled
    Check the WEOLL configuration files or admin panel for the file upload module. Look for settings related to file attachments, media uploads, or document management.
    Affected if File upload functionality is enabled and accessible to users
  3. Inspect file type validation configuration
    Examine WEOLL's configuration or settings related to allowed file types. Check for any allowlist or blocklist configurations that control what file extensions can be uploaded.
    Affected if There is no strict allowlist-based file type validation, or the validation can be bypassed
  4. Check upload directory location and script execution settings
    Locate the configured upload directory in WEOLL's configuration. Verify whether the directory is stored within the web root and whether script execution restrictions are in place.
    Affected if Uploads are stored within the web root or script execution is not disabled in the upload directory

You are affected if WEOLL version is between 2.0.9 and 3.2.45.33 (exclusive) AND file upload feature is enabled with insufficient file type restrictions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to WEOLL version 3.2.45.33 or later. Additionally, implement server-side file type validation using allowlists, store uploads outside the web root, and enforce proper ACL controls on uploaded files.

Recommended fix Moderate confidence

WEOLL version 3.2.45.33 or later

  1. Identify the currently deployed WEOLL version using the application's version information or system inventory
  2. Confirm the version is within the affected range (2.0.9 through versions before 3.2.45.33)
  3. Plan for upgrade during a maintenance window to minimize business impact
  4. Back up the current WEOLL installation including configuration files and any uploaded content
  5. Obtain the fixed version (3.2.45.33 or later) from the vendor Global IT Informatics Services Inc.
  6. Follow vendor-provided upgrade instructions for WEOLL, ensuring proper file permissions are set after upgrade
  7. Verify the upgrade was successful by checking the version number
  8. Test that file upload functionality works correctly with appropriate file type restrictions enforced

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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