CVE-2025-50090
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 Applications Framework product of Oracle E-Business Suite (component: Personalization). Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Applications Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications Framework, 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 Applications Framework accessible data as well as unauthorized read access to a subset of Oracle Applications Framework accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · moderate confidenceOracle Applications Framework Personalization component in Oracle E-Business Suite versions 12.2.3-12.2.14 contains a vulnerability exploitable via HTTP that allows low-privileged attackers with network access to achieve unauthorized read and write access to some data. The attack requires human interaction from a victim (non-attacker), suggesting a cross-site scripting (XSS) or similar injection vector through the personalization feature. The CVSS vector indicates limited scope change capability.
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>= 12.2.3, <= 12.2.14CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Oracle E-Business Suite installationCheck for Oracle E-Business Suite by querying the Oracle Applications context file (context_name.xml) in $INST_TOP/ora/10.1.2 or review Oracle Inventory (orainst). On the application server, run: 'adIdent.sh' or inspect the installation directory for EBS-specific folders.Affected if Oracle E-Business Suite is installed and the version falls within 12.2.3 to 12.2.14 inclusive
-
Determine the exact EBS versionLog into the EBS application as a user with Administrator responsibilities. Navigate to: Help > About Oracle Applications or query the 'fnd_product_installations' table using SQL: SELECT release_name FROM fnd_product_installations WHERE patch_level IS NOT NULL;Affected if The version returned is >= 12.2.3 and <= 12.2.14
-
Verify Oracle Applications Framework is accessibleAttempt to access the Oracle Applications Framework URL path '/OA_HTML/个性化功能' or check the web listener configuration for the Apache/OHS module mod_apps.conf which serves the OA_HTML directory.Affected if The Oracle Applications Framework responds to HTTP requests and OA_HTML is accessible via the web server
-
Confirm personalization feature is enabledIn EBS, navigate to: Profile > System and check the profile option 'Personalize Self-Service Interface'. Alternatively, query: SELECT profile_option_value FROM fnd_profile_option_values WHERE profile_option_id IN (SELECT profile_option_id FROM fnd_profile_options WHERE profile_option_name = 'PERSONALIZE_SS_INTERFACE');Affected if Personalization is enabled (value is 'Y' or 'Yes')
A user is affected if Oracle E-Business Suite version 12.2.3-12.2.14 is installed, the Oracle Applications Framework is network-accessible via HTTP, and the personalization feature is enabled.
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 the Oracle critical patch update for this vulnerability. Until patched, restrict network access to Oracle Applications Framework and educate users about not clicking untrusted links. Review and potentially disable personalization features if possible.
Apply the latest Oracle Critical Patch Update (CPU) that includes the fix for CVE-2025-50090; for E-Business Suite 12.2, continue applying quarterly CPUs as they are released
- 1. Monitor Oracle Critical Patch Updates (CPUs) for the release containing the fix for CVE-2025-50090.
- 2. Apply the appropriate Oracle Critical Patch Update that addresses this vulnerability in Oracle Applications Framework.
- 3. Verify the patch was applied successfully by checking the Oracle Applications Framework version and testing the Personalization component.
- 4. Confirm the CSRF protection is now enforced in the Personalization component.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.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 $10,368.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50090 — 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-50090 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