CVE-2026-62504
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 Time and Labor product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Time and Labor. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Time and Labor accessible data as well as unauthorized access to critical data or complete access to all Oracle Time and Labor accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 confidenceThis is an access control vulnerability in Oracle Time and Labor (E-Business Suite 12.2.3-12.2.15) within the Internal Operations component. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) indicates a network-based, low-complexity attack requiring low privileges that results in high confidentiality and integrity impact—allowing unauthorized creation, deletion, modification, and access to critical data via HTTP 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>= 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Verify Oracle E-Business Suite versionQuery the FND_PRODUCT_GROUPS table or run the version check script (version.sql) to obtain the EBS release version. Alternatively, inspect the context file in $APPL_TOP/admin for the release version information.Affected if The installed EBS version falls within 12.2.3 through 12.2.15 inclusive.
-
Confirm Time and Labor module is installedQuery the FND_INSTALLABLE_APPS table or check the Oracle Applications Manager (OAM) for installed modules. Look for 'Oracle Time and Labor' in the list of installed products.Affected if Oracle Time and Labor is listed as an installed or enabled module in the EBS environment.
-
Check if Internal Operations component is configuredAccess the Oracle Time and Labor responsibility in EBS and navigate to the Internal Operations functionality. Verify whether this specific component is accessible within the Time and Labor module.Affected if The Internal Operations feature is accessible or enabled within the Time and Labor module.
-
Assess network exposure of EBS web interfacesReview the Oracle E-Business Suite web tier configuration (Oracle HTTP Server or Oracle Internet Directory) to determine if the /OA_HTML/ or /servlets/ endpoints serving Time and Labor are exposed to the network.Affected if The EBS web interfaces for Time and Labor are reachable from low-privileged network attackers without proper authentication controls.
A user is affected if their Oracle EBS version is between 12.2.3 and 12.2.15 inclusive, the Time and Labor module with Internal Operations is installed, and the web interface is network-accessible to low-privileged 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.
From vendor dataApply the relevant Oracle Critical Patch Update (CPU) for this vulnerability and review access control configurations in Oracle Time and Labor Internal Operations to ensure proper authorization enforcement.
- Consultation5.0 h
- Implementation10.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,264.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62504 — 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-62504 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