CVE-2025-64515: CWE-20: Improper Input Validation in open-formulieren open-forms
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 Analysis
Technical Summary
CVE-2025-64515 is an input validation vulnerability classified under CWE-20 affecting the open-forms product by open-formulieren. 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 manipulated by malicious actors. Although the UI prevents users from modifying these fields, the underlying input validation does not enforce this restriction server-side, allowing attackers with at least limited privileges to alter data fields that should be immutable. This improper input validation flaw compromises data integrity by enabling unauthorized modifications without requiring user interaction. The vulnerability has a CVSS 3.1 base score of 4.3, reflecting a medium severity level due to its limited impact on confidentiality and availability and the requirement for some privileges to exploit. No known exploits have been reported in the wild, but the issue has been addressed in versions 3.2.7 and 3.3.3 of open-forms. Organizations using affected versions should apply these patches promptly to prevent potential data tampering. The vulnerability is particularly relevant for environments where form data integrity is critical, such as government services, financial institutions, and healthcare providers that rely on open-forms for data collection and processing.
Potential Impact
The primary impact of CVE-2025-64515 is on data integrity, as attackers can modify form data fields that should be readonly or disabled, potentially leading to inaccurate or fraudulent information being submitted and processed. For European organizations, this could undermine trust in digital forms used for regulatory reporting, customer onboarding, or internal workflows. While confidentiality and availability are not directly affected, the integrity compromise could result in compliance violations, financial losses, or operational disruptions if critical data is altered. Sectors such as public administration, financial services, and healthcare are particularly sensitive to data integrity issues and may face regulatory scrutiny under GDPR or other local data protection laws if manipulated data leads to incorrect decisions or disclosures. The requirement for some level of privileges to exploit the vulnerability reduces the risk from external attackers but does not eliminate insider threat or exploitation via compromised accounts. The absence of known exploits in the wild suggests limited current active exploitation but does not preclude future attacks if patches are not applied.
Mitigation Recommendations
European organizations should immediately verify the version of open-forms deployed and upgrade to version 3.2.7 or 3.3.3 or later where the vulnerability is patched. In addition to patching, organizations should implement strict access controls and monitoring to limit which users have privileges that could exploit this vulnerability. Input validation should be enforced server-side to ensure that readonly or disabled fields cannot be modified regardless of client-side restrictions. Conduct thorough audits of form data integrity and implement anomaly detection to identify suspicious modifications. Organizations should also review and tighten their user privilege management and consider multi-factor authentication to reduce the risk of compromised accounts being used to exploit this flaw. Finally, maintain an incident response plan that includes procedures for investigating and mitigating data integrity incidents related to form submissions.
Affected Countries
Germany, France, United Kingdom, Netherlands, Belgium, Sweden, Italy, Spain
CVE-2025-64515: CWE-20: Improper Input Validation in open-formulieren 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
Technical Analysis
CVE-2025-64515 is an input validation vulnerability classified under CWE-20 affecting the open-forms product by open-formulieren. 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 manipulated by malicious actors. Although the UI prevents users from modifying these fields, the underlying input validation does not enforce this restriction server-side, allowing attackers with at least limited privileges to alter data fields that should be immutable. This improper input validation flaw compromises data integrity by enabling unauthorized modifications without requiring user interaction. The vulnerability has a CVSS 3.1 base score of 4.3, reflecting a medium severity level due to its limited impact on confidentiality and availability and the requirement for some privileges to exploit. No known exploits have been reported in the wild, but the issue has been addressed in versions 3.2.7 and 3.3.3 of open-forms. Organizations using affected versions should apply these patches promptly to prevent potential data tampering. The vulnerability is particularly relevant for environments where form data integrity is critical, such as government services, financial institutions, and healthcare providers that rely on open-forms for data collection and processing.
Potential Impact
The primary impact of CVE-2025-64515 is on data integrity, as attackers can modify form data fields that should be readonly or disabled, potentially leading to inaccurate or fraudulent information being submitted and processed. For European organizations, this could undermine trust in digital forms used for regulatory reporting, customer onboarding, or internal workflows. While confidentiality and availability are not directly affected, the integrity compromise could result in compliance violations, financial losses, or operational disruptions if critical data is altered. Sectors such as public administration, financial services, and healthcare are particularly sensitive to data integrity issues and may face regulatory scrutiny under GDPR or other local data protection laws if manipulated data leads to incorrect decisions or disclosures. The requirement for some level of privileges to exploit the vulnerability reduces the risk from external attackers but does not eliminate insider threat or exploitation via compromised accounts. The absence of known exploits in the wild suggests limited current active exploitation but does not preclude future attacks if patches are not applied.
Mitigation Recommendations
European organizations should immediately verify the version of open-forms deployed and upgrade to version 3.2.7 or 3.3.3 or later where the vulnerability is patched. In addition to patching, organizations should implement strict access controls and monitoring to limit which users have privileges that could exploit this vulnerability. Input validation should be enforced server-side to ensure that readonly or disabled fields cannot be modified regardless of client-side restrictions. Conduct thorough audits of form data integrity and implement anomaly detection to identify suspicious modifications. Organizations should also review and tighten their user privilege management and consider multi-factor authentication to reduce the risk of compromised accounts being used to exploit this flaw. Finally, maintain an incident response plan that includes procedures for investigating and mitigating data integrity incidents related to form submissions.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
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/18/2025, 11:41:38 PM
Last updated: 11/19/2025, 2:53:02 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-12852: CWE-427: Uncontrolled Search Path Element in NEC Corporation RakurakuMusen Start EX
HighIran-Nexus Threat Actor UNC1549 Takes Aim at Aerospace
MediumCloud Break: IoT Devices Open to Silent Takeover Via Firewalls
MediumCVE-2025-65015: CWE-770: Allocation of Resources Without Limits or Throttling in authlib joserfc
CriticalCVE-2025-65012: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in getkirby kirby
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.