Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64515: CWE-20: Improper Input Validation in open-formulieren open-forms

0
Medium
VulnerabilityCVE-2025-64515cvecve-2025-64515cwe-20
Published: Tue Nov 18 2025 (11/18/2025, 22:39:48 UTC)
Source: CVE Database V5
Vendor/Project: open-formulieren
Product: open-forms

Description

Open Forms allows users create and publish smart forms. Prior to versions 3.2.7 and 3.3.3, forms where the prefill data fields are dynamically set to readonly/disabled can be modified by malicious users deliberately trying to modify data they're not supposed to. For regular users, the form fields are marked as readonly and cannot be modified through the user interface. This issue has been patched in versions 3.2.7 and 3.3.3.

AI-Powered Analysis

AILast updated: 11/26/2025, 00:16:50 UTC

Technical Analysis

CVE-2025-64515 is a vulnerability classified under CWE-20 (Improper Input Validation) found in the open-forms product by open-formulieren, which enables users to create and publish smart forms. The vulnerability exists in versions prior to 3.2.7 and between 3.3.0 and 3.3.3, where form fields that are dynamically set to readonly or disabled for regular users can still be modified by attackers. Although the user interface restricts modification by marking fields as readonly, the backend does not properly validate or enforce these restrictions, allowing malicious users with low privileges to alter data fields they should not be able to change. This bypass of client-side controls leads to unauthorized data integrity violations. The vulnerability is exploitable remotely over the network without user interaction, requiring only low-level privileges. The CVSS v3.1 score is 4.3 (medium severity), reflecting the limited impact on confidentiality and availability but a clear impact on integrity. No known exploits have been reported in the wild, and the issue has been addressed in versions 3.2.7 and 3.3.3 by improving input validation and enforcement of readonly/disabled field restrictions on the server side.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to data integrity within smart forms used for data collection, processing, or service delivery. Unauthorized modification of readonly fields could lead to inaccurate data submissions, fraud, or manipulation of critical workflows, especially in sectors like government services, healthcare, finance, and utilities where form data drives decision-making or compliance processes. While confidentiality and availability are not directly impacted, the integrity breach could undermine trust in digital forms and lead to regulatory or operational consequences. Organizations relying on open-forms for public-facing or internal forms should consider the risk of malicious insiders or external attackers exploiting this flaw to alter data undetected. The absence of known exploits suggests limited active targeting but does not eliminate the risk of future attacks once the vulnerability details are widely known.

Mitigation Recommendations

European organizations using open-forms should immediately upgrade to version 3.2.7 or 3.3.3 or later to apply the official patch that enforces proper server-side validation of readonly and disabled fields. Until patched, organizations should implement additional server-side input validation controls to reject unauthorized modifications of protected fields. Monitoring and logging form submissions for anomalous changes to readonly fields can help detect exploitation attempts. Restricting access to form management interfaces and applying the principle of least privilege reduces the risk of low-privilege users exploiting this issue. Additionally, organizations should conduct security reviews of custom form configurations to ensure no other client-side restrictions are relied upon without backend enforcement. User awareness and training on secure form usage and reporting suspicious behavior can further reduce risk.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-05T21:15:39.400Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691d040cb61595322dd84bc9

Added to database: 11/18/2025, 11:41:00 PM

Last enriched: 11/26/2025, 12:16:50 AM

Last updated: 1/7/2026, 4:17:57 AM

Views: 90

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats