CVE-2025-21550
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 Behavior Detection Platform product of Oracle Financial Services Applications (component: Web UI). Supported versions that are affected are 8.0.8.1, 8.1.2.7 and 8.1.2.8. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Financial Services Behavior Detection Platform. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Financial Services Behavior Detection Platform, 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 Financial Services Behavior Detection Platform accessible data as well as unauthorized read access to a subset of Oracle Financial Services Behavior Detection Platform 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 confidenceAn access control vulnerability in the Web UI component of Oracle Financial Services Behavior Detection Platform allows unauthenticated remote attackers to perform unauthorized read, insert, update, and delete operations on a subset of accessible data. The attack requires human interaction and can impact additional products beyond the vulnerable component due to scope change.
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.8.1= 8.1.2.7= 8.1.2.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle Financial Services Behavior Detection Platform is installedReview installed software inventory, application manifests, or deployment documentation for presence of Oracle Financial Services Behavior Detection Platform. Check application servers (WebLogic, etc.) for deployed WAR files or EAR archives containing this product.Affected if The product is not found in the environment, this CVE does not apply.
-
Determine the installed version of the productLocate version information in the product's administration console, about screen, or check version files in the installation directory. Compare against the affected versions: 8.0.8.1, 8.1.2.7, or 8.1.2.8.Affected if The installed version matches exactly 8.0.8.1, 8.1.2.7, or 8.1.2.8.
-
Verify the Web UI component is accessibleAttempt to access the Web UI login or landing page via HTTP/HTTPS. Check if the Web UI endpoint is listening on configured ports (commonly 8080, 8443, or application-specific ports). Review reverse proxy or load balancer configurations for exposed Web UI paths.Affected if The Web UI component is reachable over the network.
-
Check network exposure of the Web UI interfaceReview firewall rules, network ACLs, and security group configurations to determine if the Web UI port is exposed to untrusted networks or the public internet. Identify if the interface is accessible without VPN or authentication.Affected if The Web UI is accessible from untrusted networks or the internet.
The environment is affected if Oracle Financial Services Behavior Detection Platform versions 8.0.8.1, 8.1.2.7, or 8.1.2.8 are installed AND the Web UI component is network-accessible to untrusted users.
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.
From vendor dataApply the relevant Oracle Critical Patch Update or specific patch for this vulnerability in Oracle Financial Services Behavior Detection Platform versions 8.0.8.1, 8.1.2.7, and 8.1.2.8. Restrict network access to the Web UI interface to trusted users only as an interim control.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21550 — 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-21550 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