☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2026-61260

CVE-2026-61260 Vulnerability in Oracle
📅 PUBLISHED: 2026-07-21 21:38 UTC 🔄 UPDATED: 2026-10-08 19:49 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.23%
👁️
0.23% probability
5.8× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Country: United States License: Commercial
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
5.4
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

Business Impact: This vulnerability affects Oracle E-Business Suite, a critical enterprise resource planning (ERP) platform used extensively in finance, manufacturing, and government sectors. The Oracle HRMS (UK) module specifically handles sensitive payroll and human resources data, including personally identifiable information (PII) and salary details. A successful attack could lead to unauthorized read, update, insert, or delete access to this sensitive data, potentially violating GDPR and other data protection regulations. The likely attacker is a low-privileged insider or an external threat actor who has already gained initial access to the application, seeking to escalate privileges laterally within the HRMS module.

Vulnerability Class & Attack Vector: This is an improper access control vulnerability (CWE-284) in the UK Payroll component of Oracle HRMS (UK). The attack vector is network-based via HTTP, requiring low-privileged authentication. The vulnerability is easily exploitable, meaning the attacker does not need to bypass complex authentication mechanisms or perform specialized actions.

Urgency Assessment: The CVSS 3.1 base score is 5.4 (Medium). The EPSS exploitation probability is 0.0%, indicating no observed exploitation in the wild as of the publication date. However, the ease of exploitation (low attack complexity, low privileges required) and the sensitive nature of the data (payroll/HR) elevate the operational risk for organizations using the affected versions. The lack of a confirmed patch or public exploit does not reduce the need for immediate mitigation, as the vulnerability is trivial to chain with other low-level access.

Key Facts:

  • Vendor: Oracle
  • Affected Software: Oracle E-Business Suite, Oracle HRMS (UK) module
  • Affected Versions: 12.2.3 through 12.2.15
  • Patch Status: None available as of 2026-07-22
  • CISA KEV: Not listed.
⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

CVSS Breakdown & Threat Level

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Metric Value Explanation
AV (Attack Vector) Network The vulnerability is exploitable remotely over HTTP.
AC (Attack Complexity) Low No specialized conditions or race conditions are required. The attack is straightforward.
PR (Privileges Required) Low The attacker needs a valid low-privileged account (e.g., a standard HR user) to exploit the flaw.
UI (User Interaction) None The attack does not require any action from a victim user.
S (Scope) Unchanged The exploit cannot affect resources beyond the Oracle HRMS (UK) component's security authority.
C (Confidentiality) Low The attacker can read a subset of HRMS data, but not all data.
I (Integrity) Low The attacker can modify, insert, or delete a subset of HRMS data.
A (Availability) None The vulnerability does not affect system availability.

Qualitative Severity: Medium. The score of 5.4 reflects a moderate risk due to the combination of network exploitability and low privileges, but limited to partial data access.

EPSS Interpretation: An EPSS score of 0.0% means that as of the report date, there is no evidence of active exploitation in the wild. This is typical for a newly published CVE. However, this score is dynamic and will likely increase as proof-of-concept code or threat intelligence emerges.

Historical Comparison: This vulnerability is similar to other access control flaws in Oracle E-Business Suite, such as CVE-2022-21587 (CVSS 5.4, Oracle HRMS) and CVE-2023-21912 (CVSS 5.4, Oracle HRMS). These CVEs share the same attack vector, privileges, and impact profile, indicating a recurring pattern of insufficient authorization checks in the HRMS module.

Temporal & Environmental Considerations: The base score of 5.4 is the current risk. Without a patch, the temporal score remains unchanged. Organizations should consider the environmental score based on the sensitivity of their HR data. If the HRMS module is exposed to the internet (which is not recommended), the risk increases significantly.

Technical Deep Dive & Attack Mechanics

Root Cause Analysis: The vulnerability stems from a failure to properly enforce authorization checks on specific API endpoints or server-side functions within the UK Payroll component. The developer likely assumed that the client-side UI would restrict access, but did not validate the user's permissions on the server side for every operation. This allows a low-privileged user to craft HTTP requests that bypass the intended access controls.

Step-by-Step Attack Flow:

  1. Authentication: The attacker logs into Oracle E-Business Suite with a low-privileged account (e.g., HR_ASSISTANT).
  2. Reconnaissance: The attacker identifies the specific HTTP endpoints used by the UK Payroll module. These are typically REST or SOAP web services under paths like /OA_HTML/, /OA_JAVA/, or /oracle/apps/per/selfservice/.
  3. Crafting the Request: The attacker modifies a legitimate HTTP request (e.g., a GET request to view an employee's personal details) by changing parameters such as personId, assignmentId, or payrollActionId to values they are not authorized to access.
  4. Exploitation: The attacker sends the crafted request. The server processes the request without verifying that the authenticated user has the necessary privileges for the specific data record.
  5. Data Access/Modification: The server returns the requested data (unauthorized read) or processes the update/insert/delete operation (unauthorized write).

Attack Surface:

  • Protocol: HTTP/HTTPS
  • Ports: 8000 (default for Oracle EBS), 443 (if HTTPS is configured)
  • Interfaces: Web application front-end, SOAP web services, REST APIs.

Pre-conditions:

  • Network access to the Oracle E-Business Suite application.
  • A valid low-privileged user account.
  • The UK Payroll module must be installed and configured.

Why Standard Defenses May Fail:

  • Web Application Firewalls (WAFs): Standard WAF rules often focus on SQL injection or XSS. They may not detect a simple parameter manipulation attack that uses valid session tokens and standard HTTP methods.
  • Input Validation: The vulnerability is not about malformed input, but about missing authorization. Input validation alone cannot fix this.
  • Network Segmentation: If the HRMS module is accessible from the internal network, an attacker who has already compromised a low-level account can pivot to this vulnerability.

Vulnerable vs. Patched Code Analysis

Note: The following is a representative pseudocode example based on the vulnerability class. Actual Oracle source code is proprietary.

Vulnerable Code (Pseudocode):

// Vulnerable: No authorization check before processing request
public EmployeeDetails getEmployeeDetails(String personId, HttpServletRequest request) {
    // Assume user is authenticated
    UserSession session = getSession(request);
    // Directly query and return data
    return employeeDAO.findByPersonId(personId);
}

Patched Code (Pseudocode):

// Patched: Authorization check added
public EmployeeDetails getEmployeeDetails(String personId, HttpServletRequest request) {
    UserSession session = getSession(request);
    // Verify the user has access to this specific personId
    if (!authorizationService.canAccessPerson(session.getUserId(), personId)) {
        throw new AuthorizationException("Access denied");
    }
    return employeeDAO.findByPersonId(personId);
}

What the Patch Changes: The patch introduces a server-side authorization check (authorizationService.canAccessPerson()) before any data is retrieved or modified. This ensures that even if a low-privileged user crafts a request for a different personId, the server will deny the operation.

Regression Considerations: The patch should not introduce regressions if the authorization service is correctly implemented. However, teams should test that the new checks do not inadvertently block legitimate administrative workflows (e.g., a manager viewing their direct reports).

Timeline & Disclosure History

  • CVE Publication Date: 2026-07-21T21:38:57.382Z
  • Estimated Discovery: Unknown. The vulnerability was likely discovered through internal Oracle security research or reported by a third-party researcher.
  • Disclosure Process: Oracle is the CNA (CVE Numbering Authority) for this vulnerability. The disclosure followed standard Oracle Critical Patch Update (CPU) procedures.
  • Known Exploitation in the Wild: No known active exploitation as of 2026-07-22.
  • CISA KEV: Not listed.

Threat Intelligence Context

Threat Actor Profile: This vulnerability is most likely to be exploited by:

  • Insider Threats: A disgruntled or malicious employee with low-level HR access seeking to exfiltrate salary data or modify payroll records.
  • Initial Access Brokers (IABs): Threat actors who have already compromised a low-privileged account via phishing or credential theft. They would use this CVE to escalate their access within the EBS environment.
  • Nation-State Actors: APT groups targeting government or defense contractors that use Oracle EBS for HR management.

Attack Campaign Context: This CVE is not currently associated with any known broader campaign. It is a standalone vulnerability.

Geographic Targeting: The vulnerability is specific to the UK Payroll module, making organizations operating in the United Kingdom or using UK-specific payroll regulations the primary targets.

Industry Verticals Most at Risk:

  • Government (central and local)
  • Healthcare
  • Financial Services
  • Manufacturing
  • Retail (large enterprises)

Historical Connection: This vulnerability is part of a long-standing pattern of access control issues in Oracle E-Business Suite. Similar CVEs (e.g., CVE-2022-21587, CVE-2023-21912) have been exploited in targeted attacks against the public sector.

Exploitation & Lab Setup

Red Team Section

Lab Setup:

  1. Environment: Oracle E-Business Suite Release 12.2.3 (or any version up to 12.2.15) installed on a virtual machine (e.g., Oracle VM VirtualBox). The UK Payroll module must be configured.
  2. Network: The VM should be on an isolated network segment. The attacker machine (e.g., Kali Linux) should be on the same network.
  3. Credentials: Create a low-privileged user account (e.g., test_user) with a role that has minimal access to HR data.

Exploitation Walkthrough:

  1. Login: Use a web proxy (e.g., Burp Suite) to intercept traffic. Log in as test_user.
  2. Identify Endpoint: Navigate to the "View Person" screen in the UK Payroll module. The browser will make a request similar to:
    GET /OA_HTML/OA.jsp?OAFunc=PERWSSCP&personId=100 HTTP/1.1
    
  3. Craft Malicious Request: Change the personId parameter to a value belonging to a different employee (e.g., personId=200).
    GET /OA_HTML/OA.jsp?OAFunc=PERWSSCP&personId=200 HTTP/1.1
    
  4. Send Request: Forward the modified request.
  5. Expected Output: If the vulnerability is present, the server will return the details of employee 200, even though test_user is not authorized to view them. If the server returns an "Access Denied" or "Unauthorized" error, the system is patched.

Post-Exploitation: After gaining unauthorized read access, the attacker can:

  • Exfiltrate PII (names, addresses, bank details).
  • Modify salary data (if the endpoint supports update operations).
  • Create fake employee records for payroll fraud.

Blue Team Section

Detection:

  • Log Entries: Look for HTTP 200 responses to requests that should have resulted in a 403 Forbidden. Specifically, monitor for requests to /OA_HTML/OA.jsp or similar paths where the personId or assignmentId parameter values are outside the expected range for the authenticated user.
  • Network Traffic: Anomalous patterns of GET/POST requests to HRMS endpoints with varying personId values in a short period.
  • Endpoint Indicators: Unusual database queries originating from the application server that retrieve a large number of employee records.

Indicators of Compromise (IOCs)

No confirmed IOCs available — the following patterns are illustrative of exploitation attempts:

Type Value Description
HTTP Request Pattern GET /OA_HTML/OA.jsp?OAFunc=PERWSSCP&personId=[0-9]+ Repeated requests to the same function with different personId values.
HTTP Request Pattern POST /OA_HTML/OA.jsp?OAFunc=PERWSSUP&personId=[0-9]+ Attempts to update employee data for unauthorized users.
Source IP [EXAMPLE — not a real IOC] A single IP address making hundreds of requests to HRMS endpoints in a short time.
User Agent [EXAMPLE — not a real IOC] Non-standard user agents (e.g., python-requests/2.28.0) used in HRMS requests.

Detection Engineering

YARA Rule

rule CVE-2026-61260_Oracle_HRMS_Access_Control {
    meta:
        description = "Detects exploitation of CVE-2026-61260 in Oracle EBS HRMS (UK) Payroll"
        author = "Valters IT Hub"
        date = "2026-07-22"
        reference = "https://www.valtersit.com/cve/cve-2026-61260"
    strings:
        $s1 = "OAFunc=PERWSSCP" ascii wide nocase
        $s2 = "personId=" ascii wide nocase
        $s3 = "assignmentId=" ascii wide nocase
    condition:
        all of ($s1, $s2, $s3) and filesize < 10KB
}

Sigma Rule (SIEM)

title: CVE-2026-61260 Oracle HRMS Unauthorized Access Attempt
id: 9b8fe0ef-7fcc-4896-b902-e30254ce86b3
status: experimental
description: Detects potential exploitation of CVE-2026-61260 by monitoring for HTTP 200 responses to HRMS endpoints that should be restricted.
author: Valters IT Hub
date: 2026-07-22
references:
    - https://www.valtersit.com/cve/cve-2026-61260
logsource:
    category: webserver
    product: apache
    service: httpd
detection:
    selection:
        cs-uri-query|contains:
            - 'OAFunc=PERWSSCP'
            - 'OAFunc=PERWSSUP'
        sc-status: 200
    filter:
        cs-username|contains:
            - 'SYSADMIN'
            - 'HR_MANAGER'
    condition: selection and not filter
falsepositives:
    - Legitimate administrative activity where a user with elevated privileges is performing bulk operations.
level: high

Suricata IDS Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2026-61260 Oracle HRMS Unauthorized Access Attempt"; flow:to_server,established; content:"OAFunc=PERWSSCP"; http_uri; content:"personId="; http_uri; pcre:"/personId=\d{3,}/R"; classtype:attempted-recon; sid:10000001; rev:1;)

Elastic (EQL) Query

sequence by source.ip
  [network where http.request.method == "GET" and
   url.path == "/OA_HTML/OA.jsp" and
   url.query : "*OAFunc=PERWSSCP*" and
   url.query : "*personId=*"]
  [network where http.response.status_code == 200]

Splunk SPL Query

index=web sourcetype=access_combined
| search uri_path="/OA_HTML/OA.jsp" uri_query="*OAFunc=PERWSSCP*" status=200
| stats count by src_ip, user, uri_query
| where count > 10
| table _time, src_ip, user, uri_query, count

Wazuh Rule

<group name="oracle_ebs,">
  <rule id="100001" level="10">
    <decoded_as>json</decoded_as>
    <field name="url">\.*\/OA_HTML\/OA\.jsp</field>
    <field name="url_query">OAFunc=PERWSSCP</field>
    <field name="status">200</field>
    <description>CVE-2026-61260: Possible unauthorized access to Oracle HRMS data.</description>
    <mitre>
      <id>T1190</id>
    </mitre>
  </rule>
</group>

Remediation & Mitigation

Immediate Actions (0-24 hours)

  1. Apply Patch: Check Oracle's support portal (My Oracle Support) for a patch for the UK Payroll module. Apply the patch to the affected versions (12.2.3-12.2.15).
  2. Compensating Controls (if no patch):
    • Network Segmentation: Ensure the Oracle EBS application is not directly accessible from the internet. Place it behind a VPN or bastion host.
    • Web Application Firewall (WAF): Create a custom WAF rule to block requests to /OA_HTML/OA.jsp that contain OAFunc=PERWSSCP or OAFunc=PERWSSUP from non-privileged user accounts. This is a temporary measure.
  3. Access Control Hardening: Review and restrict the privileges of all low-level HR users. Remove unnecessary access to the UK Payroll module.

Short-term (1-7 days)

  1. Configuration Hardening: Implement the principle of least privilege for all EBS roles. Use Oracle's Role-Based Access Control (RBAC) to ensure users can only access the data they need.
  2. Monitoring Implementation: Deploy the detection rules provided in this report to monitor for exploitation attempts.
  3. Vulnerability Scanning: Run a vulnerability scanner (e.g., Qualys, Nessus) against the EBS instance to confirm the patch has been applied. The scanner should report the CVE as resolved.

Long-term

  1. Architecture Changes: Consider migrating to Oracle Cloud HCM or a modern SaaS-based HR solution to reduce the attack surface of on-premise EBS.
  2. Security Control Improvements: Implement a robust API gateway with fine-grained authorization for all EBS web services.
  3. Developer Training: Train developers on secure coding practices, specifically focusing on server-side authorization checks (OWASP Top 10: A01 - Broken Access Control).

Validation

To confirm the patch is applied:

  1. Log in as a low-privileged user.
  2. Attempt to access a record you should not have access to (e.g., a different employee's details).
  3. Verify that the server returns an "Access Denied" or "Unauthorized" error.
  4. Check the Oracle EBS patch inventory via the AD Patch History form.

References & Resources


Report generated by Valters IT Hub Neural Engine v25 | 2026-07-22 | https://www.valtersit.com/cve/cve-2026-61260

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-61260/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.