CVE-2025-12921: XML Injection in OpenClinica Community Edition
A vulnerability has been found in OpenClinica Community Edition up to 3.12.2/3.13. Affected by this issue is some unknown functionality of the file /ImportCRFData?action=confirm of the component CRF Data Import. Such manipulation of the argument xml_file leads to xml injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AI Analysis
Technical Summary
CVE-2025-12921 is a medium-severity XML injection vulnerability identified in OpenClinica Community Edition versions 3.0 through 3.13. The vulnerability resides in the CRF Data Import component, specifically in the /ImportCRFData?action=confirm endpoint. The xml_file parameter, which is intended to accept XML data for importing case report forms (CRFs), lacks sufficient input validation and sanitization, allowing an attacker to inject malicious XML content. This injection can alter the structure or content of the XML data processed by the application, potentially leading to unauthorized data manipulation, corruption of clinical trial data, or disruption of data import workflows. The attack vector is remote network access without requiring authentication or user interaction, increasing the risk of exploitation. Despite early notification, the vendor has not issued patches or advisories, leaving systems exposed. The CVSS 4.0 vector indicates low complexity to exploit (AC:L), no privileges required (PR:L), no user interaction (UI:N), and partial impact on confidentiality (VC:L) but no impact on integrity or availability. No known exploits are currently observed in the wild, but public disclosure increases the risk of future exploitation. The vulnerability affects a critical component used in clinical research data management, making it a significant concern for organizations relying on OpenClinica for regulatory-compliant data collection and analysis.
Potential Impact
For European organizations, particularly those involved in clinical research, pharmaceutical trials, and healthcare data management, this vulnerability poses a risk to the confidentiality and integrity of sensitive clinical trial data. Successful exploitation could allow attackers to inject malicious XML payloads that manipulate or corrupt case report form data, potentially invalidating research results or causing regulatory compliance issues. Disruption of data import processes could delay clinical trials or lead to erroneous conclusions. Given the sensitive nature of clinical data, breaches could also result in reputational damage and legal consequences under GDPR. The lack of vendor response and patches increases exposure time, raising the likelihood of targeted attacks. Organizations using affected OpenClinica versions without compensating controls are particularly vulnerable. The impact extends to research institutions, contract research organizations (CROs), and healthcare providers across Europe that rely on OpenClinica for data collection and management.
Mitigation Recommendations
1. Immediately restrict network access to the /ImportCRFData?action=confirm endpoint using firewalls or application-layer access controls to limit exposure to trusted IPs or internal networks only. 2. Implement strict input validation and XML schema validation on all incoming XML data to ensure only well-formed and expected XML structures are processed. 3. Employ XML parsing libraries with secure configurations that disable external entity processing and other risky XML features to prevent injection attacks. 4. Monitor application logs and import activities for unusual or malformed XML submissions that could indicate exploitation attempts. 5. If feasible, upgrade to a newer OpenClinica version or apply vendor patches once available. 6. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XML injection patterns targeting the vulnerable endpoint. 7. Conduct security awareness and training for staff managing clinical data imports to recognize suspicious activities. 8. Engage with OpenClinica community or vendors to advocate for timely patch releases and share threat intelligence. 9. As a temporary measure, disable or limit the use of the CRF Data Import feature if it is not critical to operations.
Affected Countries
Germany, United Kingdom, France, Netherlands, Sweden, Switzerland, Belgium
CVE-2025-12921: XML Injection in OpenClinica Community Edition
Description
A vulnerability has been found in OpenClinica Community Edition up to 3.12.2/3.13. Affected by this issue is some unknown functionality of the file /ImportCRFData?action=confirm of the component CRF Data Import. Such manipulation of the argument xml_file leads to xml injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AI-Powered Analysis
Technical Analysis
CVE-2025-12921 is a medium-severity XML injection vulnerability identified in OpenClinica Community Edition versions 3.0 through 3.13. The vulnerability resides in the CRF Data Import component, specifically in the /ImportCRFData?action=confirm endpoint. The xml_file parameter, which is intended to accept XML data for importing case report forms (CRFs), lacks sufficient input validation and sanitization, allowing an attacker to inject malicious XML content. This injection can alter the structure or content of the XML data processed by the application, potentially leading to unauthorized data manipulation, corruption of clinical trial data, or disruption of data import workflows. The attack vector is remote network access without requiring authentication or user interaction, increasing the risk of exploitation. Despite early notification, the vendor has not issued patches or advisories, leaving systems exposed. The CVSS 4.0 vector indicates low complexity to exploit (AC:L), no privileges required (PR:L), no user interaction (UI:N), and partial impact on confidentiality (VC:L) but no impact on integrity or availability. No known exploits are currently observed in the wild, but public disclosure increases the risk of future exploitation. The vulnerability affects a critical component used in clinical research data management, making it a significant concern for organizations relying on OpenClinica for regulatory-compliant data collection and analysis.
Potential Impact
For European organizations, particularly those involved in clinical research, pharmaceutical trials, and healthcare data management, this vulnerability poses a risk to the confidentiality and integrity of sensitive clinical trial data. Successful exploitation could allow attackers to inject malicious XML payloads that manipulate or corrupt case report form data, potentially invalidating research results or causing regulatory compliance issues. Disruption of data import processes could delay clinical trials or lead to erroneous conclusions. Given the sensitive nature of clinical data, breaches could also result in reputational damage and legal consequences under GDPR. The lack of vendor response and patches increases exposure time, raising the likelihood of targeted attacks. Organizations using affected OpenClinica versions without compensating controls are particularly vulnerable. The impact extends to research institutions, contract research organizations (CROs), and healthcare providers across Europe that rely on OpenClinica for data collection and management.
Mitigation Recommendations
1. Immediately restrict network access to the /ImportCRFData?action=confirm endpoint using firewalls or application-layer access controls to limit exposure to trusted IPs or internal networks only. 2. Implement strict input validation and XML schema validation on all incoming XML data to ensure only well-formed and expected XML structures are processed. 3. Employ XML parsing libraries with secure configurations that disable external entity processing and other risky XML features to prevent injection attacks. 4. Monitor application logs and import activities for unusual or malformed XML submissions that could indicate exploitation attempts. 5. If feasible, upgrade to a newer OpenClinica version or apply vendor patches once available. 6. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XML injection patterns targeting the vulnerable endpoint. 7. Conduct security awareness and training for staff managing clinical data imports to recognize suspicious activities. 8. Engage with OpenClinica community or vendors to advocate for timely patch releases and share threat intelligence. 9. As a temporary measure, disable or limit the use of the CRF Data Import feature if it is not critical to operations.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-11-09T06:42:36.062Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69112787a0a00dcacbece57c
Added to database: 11/9/2025, 11:45:11 PM
Last enriched: 11/9/2025, 11:45:26 PM
Last updated: 11/10/2025, 4:44:06 AM
Views: 6
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-62689: Heap-based buffer overflow in GNU Project GNU libbmicrohttpd
HighCVE-2025-59777: NULL pointer dereference in GNU Project GNU libbmicrohttpd
HighCVE-2025-12930: SQL Injection in SourceCodester Food Ordering System
MediumCVE-2025-12929: SQL Injection in SourceCodester Survey Application System
MediumCVE-2025-12928: SQL Injection in code-projects Online Job Search Engine
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.