dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-1126

MEDIUM · 6.3 CVSS v3.1 Published 2026-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A security vulnerability has been detected in lwj flow up to a3d2fe8133db9d3b50fda4f66f68634640344641. This affects the function uploadFile of the file \flow-master\flow-front-rest\src\main\java\com\dragon\flow\web\resource\flow\FormResource.java of the component SVG File Handler. The manipulation of the argument File leads to unrestricted upload. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

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 lwj flow's FormResource.java uploadFile function. The SVG file handler accepts files without proper validation, allowing attackers to upload malicious files by manipulating the File argument. This can lead to remote code execution if uploaded files are accessible for execution.

MitigationImplement strict file type validation (allowlist approach), validate file content/magic bytes rather than just extensions, store uploads outside webroot with randomized filenames, and disable script execution in upload directories.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify lwj flow installation and version
    Search for lwj flow application files, check application manifest, or query the web application for version information
    Affected if lwj flow is installed and the version matches or falls within affected ranges (no specific version ranges provided, compare against any known vulnerable version)
  2. Locate FormResource.java upload endpoint
    Examine web application routing or WAR file structure to identify the upload endpoint served by FormResource.java
    Affected if The FormResource.java uploadFile function is exposed as a web accessible endpoint
  3. Verify SVG file upload is permitted
    Test the upload endpoint with an SVG file or inspect the file type validation logic in FormResource.java
    Affected if SVG files can be uploaded without proper content-type or content validation
  4. Check upload directory placement
    Inspect the upload storage configuration - verify if uploads are stored inside or outside the webroot
    Affected if Uploaded files are stored within the webroot and accessible via HTTP
  5. Confirm script execution is not disabled in upload directory
    Check web server configuration (e.g., .htaccess, web.xml, server config) for script execution settings in the upload directory
    Affected if Script execution is enabled in the upload directory, allowing uploaded files to be executed

A user is affected if lwj flow with the vulnerable FormResource.java upload function is deployed, the upload endpoint is accessible, and uploaded SVG files can be accessed and executed from the webroot.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation (allowlist approach), validate file content/magic bytes rather than just extensions, store uploads outside webroot with randomized filenames, and disable script execution in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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