dbcve.org
Bi PublisherApplication · Oracle

CVE-2025-30723

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 BI Publisher product of Oracle Analytics (component: XML Services). Supported versions that are affected are 7.6.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle BI Publisher accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle BI Publisher. CVSS 3.1 Base Score 5.4 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L).

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

This is an XML injection vulnerability in Oracle BI Publisher's XML Services component. A low-privileged attacker with network access via HTTP can exploit this to perform unauthorized update, insert, or delete operations on accessible data, and cause a partial denial of service. The CVSS vector indicates no confidentiality impact but low integrity and availability impacts.

MitigationApply Oracle's security patches for versions 7.6.0.0.0 and 12.2.1.4.0 when available. Until then, restrict network access to BI Publisher, implement input validation via WAF for XML submissions, and monitor for suspicious XML service requests.

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
Bi PublisherApplication
Affected:= 7.6.0.0.0= 12.2.1.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 BI Publisher installation and version
    Locate the BI Publisher installation directory and check the version. Common locations include $ORACLE_HOME/bipublisher or check the about page at /xmlpserver/about.jsp. Use the system's inventory or package manager if deployed via enterprise software distribution.
    Affected if The installed version matches exactly 7.6.0.0.0 or 12.2.1.4.0
  2. Identify if XML Services component is enabled
    Check the BI Publisher administration console or configuration files for the XML Services module. This is typically accessible via the /xmlpserver/services endpoint. Review the bipublisher-config.xml or similar configuration files for XML Services enablement.
    Affected if XML Services component is exposed and accessible via HTTP endpoint
  3. Verify network accessibility of XML Services endpoint
    Determine if the XML Services HTTP endpoint is reachable from the network. Test connectivity to common XML Services paths such as /xmlpserver/services/ or check the server's firewall and reverse proxy configuration.
    Affected if The XML Services endpoint is accessible over network without proper segmentation or authentication enforcement
  4. Check for existing input validation on XML submissions
    Review Web Application Firewall (WAF) configurations or BI Publisher input validation settings for XML Service requests. Inspect any proxy or gateway logs for XML injection patterns.
    Affected if No input validation layer exists between external users and the XML Services endpoint

You are affected if Oracle BI Publisher version 7.6.0.0.0 or 12.2.1.4.0 is installed AND the XML Services component is enabled and network-accessible.

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 Oracle's security patches for versions 7.6.0.0.0 and 12.2.1.4.0 when available. Until then, restrict network access to BI Publisher, implement input validation via WAF for XML submissions, and monitor for suspicious XML service requests.

Fix this in Bi Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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