CVE-2026-46955
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 Human Resources product of Oracle E-Business Suite (component: Person). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Human Resources. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Human Resources. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
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 confidenceSQL injection vulnerability in the Person component of Oracle Human Resources (E-Business Suite 12.2.3-12.2.15) allows unauthenticated remote attackers to execute arbitrary SQL commands via crafted HTTP requests. The requirement for human interaction suggests the attacker must trick a legitimate user into performing an action (e.g., clicking a malicious link) to facilitate the attack chain leading to complete system takeover.
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.15CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
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 installation and versionCheck the Oracle Applications version by accessing the login page HTML source, checking the about page, or querying the database (FND_PRODUCT_GROUPS or similar). Alternatively, check the environment or configuration files that store the EBS version.Affected if The installed version is between 12.2.3 and 12.2.15 inclusive
-
Confirm the Person component is enabledVerify that the Human Resources module and its Person component are accessible in the EBS environment. Check the functional responsibility setup and module availability.Affected if The Person component is enabled and accessible to users
-
Check if HTTP endpoints for Person component are exposedIdentify if web URLs for the Person component (typically under /OA_HTML/ or similar HR-related paths) are exposed externally without proper network segmentation or authentication barriers.Affected if The Person component HTTP endpoints are externally accessible without additional authentication layers
-
Review existing input validation or WAF coverageInspect whether a Web Application Firewall (WAF) or custom input validation filters are deployed in front of the EBS application, particularly for the Person component endpoints.Affected if No WAF or input validation is in place to detect and block anomalous SQL injection patterns in HTTP requests to the Person component
A user is affected if they have Oracle E-Business Suite version 12.2.3 through 12.2.15 with the Person component enabled and accessible, and without WAF or input validation controls blocking SQL injection attempts.
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 Oracle Critical Patch Update for Oracle E-Business Suite. Prior to production deployment, test thoroughly in a non-production environment as Oracle E-Business Suite patches can affect HR workflows. Implement web application firewall (WAF) rules as an interim control to detect and block anomalous HTTP requests to the Person component.
- 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-2026-46955 — 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-2026-46955 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