CVE-2025-53035
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 · uneditedVulnerability in the Oracle Financial Services Analytical Applications Infrastructure product of Oracle Financial Services Applications (component: Platform). Supported versions that are affected are 8.0.7.9, 8.0.8.7 and 8.1.2.5. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Financial Services Analytical Applications Infrastructure. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Financial Services Analytical Applications Infrastructure accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 confidenceVulnerability in Oracle Financial Services Analytical Applications Infrastructure (Platform component) allows low-privileged attackers with network access via HTTP to gain unauthorized access to critical data. The attack requires no user interaction and exploits the platform component in affected versions 8.0.7.9, 8.0.8.7, and 8.1.2.5, resulting in high confidentiality impact with no integrity or availability impact.
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= 8.0.7.9.0= 8.0.8.7.0= 8.1.2.5.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Financial Services Analytical Applications Infrastructure installationLocate the OFSAA installation directory or check for OFSAA-related processes/services on the system. Common locations include /opt/oracle/ofsaa or C:\Oracle\ofsaa on Windows servers.Affected if OFSAA Infrastructure software is not found on the system, the vulnerability does not apply.
-
Determine installed OFSAA Infrastructure versionLocate the version file or check the OFSAA release information. Typical locations include version.txt in the installation directory or within the About section of the OFSAA web interface.Affected if The installed version matches exactly 8.0.7.9.0, 8.0.8.7.0, or 8.1.2.5.0, the system is running a vulnerable version.
-
Verify Platform component is network accessibleDetermine if the OFSAA Platform component is exposed to the network via HTTP/HTTPS. Check network listener configurations, load balancer settings, or firewall rules that allow external access to the Platform component ports.Affected if The Platform component is reachable from untrusted networks over HTTP, the vulnerability is exploitable from those network paths.
-
Review network access controls on Platform componentExamine firewall rules, web server access controls, or network segmentation applied to the OFSAA Platform component. Identify whether low-privileged users or untrusted IP addresses can reach the component.Affected if Low-privileged attackers can reach the Platform component over the network without additional authentication barriers, they could exploit this vulnerability.
A user is affected if they have Oracle Financial Services Analytical Applications Infrastructure versions 8.0.7.9.0, 8.0.8.7.0, or 8.1.2.5.0 installed with the Platform component accessible to low-privileged network attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Oracle's official security patches for this vulnerability when available. As a compensating control, restrict network access to the Platform component to only authorized users and systems until the patch can be applied.
- Contact Oracle Support to obtain the specific security patch for CVE-2025-53035
- Request the latest Oracle Critical Patch Update (CPU) that addresses this vulnerability
- Apply the security patch following Oracle's standard patch deployment procedures for Oracle Financial Services Analytical Applications Infrastructure
- After patching, verify the fix by confirming the Platform component has been updated
- Test that low-privileged users can no longer access data beyond their authorized scope
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53035 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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