Skip to main content
CVE-2025-12922VulnerabilityPublished Updated

CVE-2025-12922: OpenClinica Community Edition · Path Traversal

Affects OpenClinica Community EditionSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
OpenClinica Community EditionAffected
  • =3.0
  • =3.1
  • =3.2
  • =3.3
  • =3.4
  • =3.5
  • =3.6
  • =3.7
  • =3.8
  • =3.9
  • =3.10
  • =3.11
  • =3.12
  • =3.12.0
  • =3.12.1
  • =3.12.2
  • =3.13
Fixed in–

AI-suggested

1. Immediately restrict network access to the /ImportCRFData?action=confirm endpoint by implementing IP whitelisting or VPN-only access to limit exposure to trusted users. 2. Deploy a web application firewall (WAF) with rules specifically designed to detect and block path traversal attempts targeting the xml_file parameter. 3. Conduct thorough logging and monitoring of access to the vulnerable endpoint, setting alerts for suspicious patterns indicative of path traversal attacks. 4. Isolate OpenClinica servers within segmented network zones to minimize lateral movement in case of compromise. 5. Review and harden file system permissions on the server to ensure the application process has minimal access rights, preventing unauthorized file reads. 6. Consider temporary disabling or restricting the CRF Data Import functionality if feasible until a vendor patch or official fix is available. 7. Engage with the OpenClinica community or security forums for potential unofficial patches or workarounds. 8. Prepare incident response plans specific to potential data breaches involving clinical data. 9. Regularly update and audit all components of the clinical data management infrastructure for additional vulnerabilities.

Description

A vulnerability was found in OpenClinica Community Edition up to 3.12.2/3.13. This affects an unknown part of the file /ImportCRFData?action=confirm of the component CRF Data Import. Performing manipulation of the argument xml_file results in path traversal. The attack can be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…