LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31041: Insufficient content-type validation for uploaded files in open-forms

Open Forms is an application for creating and publishing smart forms. Open Forms supports file uploads as one of the form field types. These fields can be configured to allow only certain file extensions to be uploaded by end users (e.g. only PDF / Excel / ...). The input validation of uploaded files is insufficient in versions prior to 1.0.9 and 1.1.1. Users could alter or strip file extensions to bypass this validation. This results in files being uploaded to the server that are of a different file type than indicated by the file name extension. These files may be downloaded (manually or automatically) by staff and/or other applications for further processing. Malicious files can therefore find their way into internal/trusted networks. Versions 1.0.9 and 1.1.1 contain patches for this issue. As a workaround, an API gateway or intrusion detection solution in front of open-forms may be able to scan for and block malicious content before it reaches the Open Forms application.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Open Forms allowed uploaded files to bypass configured extension restrictions before versions 1.0.9 and 1.1.1. A user could make a file appear acceptable by altering or removing its extension, letting unexpected file types reach the server and potentially staff or internal processing systems.

Executive priority

Treat this as a high-priority application hardening issue if Open Forms handles external uploads. The primary risk is malicious content entering trusted workflows, not proven remote compromise from the sources provided. Patch promptly and review upload-processing practices.

Technical view

CVE-2022-31041 is insufficient uploaded-file validation in open-formulieren open-forms. File upload fields could enforce allowed extensions, but validation before 1.0.9 and affected 1.1.0 release candidates could be bypassed by changing or stripping extensions. The issue is classified as CWE-20 and CWE-434 with CVSS 3.1 score 7.6.

Likely exposure

Exposure is likely where Open Forms is internet- or network-accessible, uses file upload fields, and runs versions below 1.0.9 or 1.1.0-rc0 through below 1.1.1. Risk depends on whether uploaded files are later downloaded or processed by staff or internal applications.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The vendor advisory describes a low-complexity network issue requiring low privileges and no user interaction in the CVSS vector, but the business impact depends on downstream handling of uploaded files.

Researcher notes

The evidence supports an upload validation bypass, not arbitrary code execution. The affected ranges are clearly identified, and patches are named. Public sources provided do not establish exploit availability, active exploitation, or specific downstream product impacts beyond unsafe files reaching internal or trusted networks.

Mitigation direction

  • Upgrade open-forms to version 1.0.9, 1.1.1, or later.
  • Check vendor guidance for any newer supported release recommendations.
  • Use an API gateway or IDS to scan and block malicious uploaded content.
  • Restrict file upload fields to necessary users and workflows.
  • Review staff and application handling of uploaded files.

Validation and detection

  • Inventory deployed open-forms versions and compare against affected ranges.
  • Identify forms with file upload fields and configured extension allow-lists.
  • Confirm patched versions reject mismatched uploaded file content.
  • Review historical uploads for unexpected file types before the patch date.
  • Verify gateway or IDS scanning is active for upload paths.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31041 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2022-31041Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
open-formulierenopen-forms< 1.0.9, >= 1.1.0-rc0, < 1.1.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.