Quick answers
- Is CVE-2026-62504 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62504 being exploited in the wild.
- How severe is CVE-2026-62504?
- High severity, with a CVSS score of 8.1, published 21 July 2026.
- Which products and versions are affected?
- Oracle Time and Labor 12.2.3-12.2.15.
- Is there a fix for CVE-2026-62504?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-62504 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-62504?
- Check whether you run Oracle Time and Labor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability affects the Internal Operations component of Oracle Time and Labor within Oracle E-Business Suite versions 12.2.3 through 12.2.15. It is classified as an easily exploitable flaw that requires only low-privileged authentication and can be triggered remotely via HTTP. An attacker can achieve high confidentiality and integrity impacts, allowing for the unauthorized viewing, creation, modification, or deletion of all data accessible to the Time and Labor module. The vulnerability does not impact system availability (A:N). Users are advised to refer to the Oracle Critical Patch Update for July 2026 for remediation steps.
Affected products
- Oracle Corporation Oracle Time and Labor 12.2.3-12.2.15
Timeline
- 2026-07-21: advisory: Oracle published the vulnerability details in the July 2026 CPU.
- 2026-07-21: disclosed: CVE-2026-62504 was published to the NVD.