dbcve.org
Life Sciences InformApplication · Oracle

CVE-2026-34324

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

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 Life Science Applications (component: App Server). Supported versions that are affected are 7.0.1.0 and 7.0.1.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Life Sciences InForm. 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.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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-based vulnerability in Oracle Life Sciences InForm App Server (versions 7.0.1.0-7.0.1.1) allows remote attackers to perform unauthorized read, insert, update, and delete operations on a subset of accessible data via the network without any credentials.

MitigationApply the Oracle-supplied patch for InForm 7.0.1.x or upgrade to a patched version. If no patch available, restrict network access to the App Server via firewall or web application firewall until Oracle releases a fix.

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= 7.0.1.1

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Confirm Oracle Life Sciences InForm installation
    Check system inventory or look for InForm installation directories. On Windows, check Program Files for 'Oracle' or 'InForm' folders. On Linux/Unix, check common application paths like /opt/oracle/ or /opt/inform/. Check services list for 'InForm' or 'Oracle Life Sciences' services.
    Affected if Oracle Life Sciences InForm App Server is present on the system
  2. Identify installed InForm version
    Check the InForm App Server version. Common locations: version file in installation directory (often version.txt, about.html, or in the app server's admin interface), or check the Windows Registry under HKLM\SOFTWARE\Oracle\InForm if installed on Windows. Look for the exact version number displayed.
    Affected if Version is 7.0.1.0 or 7.0.1.1 (the specific affected versions)
  3. Verify HTTP listener is exposed
    Determine if the InForm App Server HTTP port is accessible from the network. Check the app server configuration for the HTTP port (commonly 80, 443, or custom ports like 8080, 8443). Use netstat or similar tool to identify listening ports associated with InForm, then verify if those ports are bound to 0.0.0.0 (all interfaces) rather than localhost only.
    Affected if HTTP/HTTPS listener is bound to a network-accessible IP address and port
  4. Check for unauthorized data access indicators
    Review InForm application logs for unusual or unauthenticated HTTP requests, especially those performing data operations (SELECT, INSERT, UPDATE, DELETE) from unfamiliar IP addresses or at unusual times. Check for failed authentication attempts or requests bypassing authentication entirely.
    Affected if Logs show data operations from unauthenticated sources or unexpected IP addresses

Environment is affected if Oracle Life Sciences InForm App Server version 7.0.1.0 or 7.0.1.1 is installed with its HTTP interface accessible over the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle-supplied patch for InForm 7.0.1.x or upgrade to a patched version. If no patch available, restrict network access to the App Server via firewall or web application firewall until Oracle releases a fix.

Fix this in Life Sciences Inform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34324 — 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-2026-34324 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