dbcve.org
Life Sciences InformApplication · Oracle

CVE-2025-62287

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Life Sciences InForm product of Oracle Health Sciences Applications (component: Web Server). The supported version that is affected is 7.0.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Life Sciences InForm. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Life Sciences InForm, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Life Sciences InForm accessible data as well as unauthorized read access to a subset of Oracle Life Sciences InForm accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated HTTP vulnerability in Oracle Life Sciences InForm 7.0.1.0 Web Server component allows remote attackers to read and modify a subset of data without credentials, requiring human interaction to exploit.

MitigationApply Oracle's security patch for version 7.0.1.0 and verify the web server configuration restricts unauthorized access to data endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Life Sciences InformApplication
Affected:= 7.0.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed InForm version
    Check the Oracle Life Sciences InForm installation directory, typically found in the program files or via the application's 'About' or version information page accessible through the web interface
    Affected if The installed version is exactly 7.0.1.0
  2. Confirm the Web Server component is running
    Locate and examine the InForm Web Server process or service (commonly named 'InFormWeb' or similar in Windows Services or process list) and verify it is actively running
    Affected if The Web Server component is running and exposed
  3. Determine if the web interface is network-accessible
    Attempt to access the InForm login page or data endpoints over HTTP/HTTPS from a non-localhost source, or review firewall and network configuration for rules allowing access to the web server ports
    Affected if The web server is reachable from network locations beyond localhost without authentication barriers
  4. Verify data endpoint accessibility without credentials
    Inspect the web application's data endpoints or API paths (such as those handling study data or user information) and confirm they respond to unauthenticated requests or return partial data without presenting a login challenge
    Affected if Data endpoints are accessible or return partial content without requiring valid authentication credentials

If your environment runs Oracle Life Sciences InForm version 7.0.1.0 with the Web Server component exposed and accessible, and data endpoints respond without authentication, your environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patch for version 7.0.1.0 and verify the web server configuration restricts unauthorized access to data endpoints.

Recommended fix Moderate confidence

Contact Oracle for the specific fixed version/patch (Oracle CPUs typically address multiple CVEs)

  1. Contact Oracle Support to request the specific patch for CVE-2025-62287
  2. Apply the Oracle Critical Patch Update (CPU) that addresses this vulnerability after obtaining it from Oracle
  3. Verify the patch was applied successfully by reviewing the Web Server component version
  4. Test the application to confirm the authentication fix is working as expected
  5. Monitor Oracle's Security Alert documentation for any follow-up patches or updates
Caveat Test thoroughly in a non-production environment before applying to production, as Oracle patches may include other changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Life Sciences Inform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62287 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data