Threats / Oracle / CVE-2025-61882
CVE-2025-61882
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle E-Business Suite vulnerability
Oracle E-Business Suite BI Publisher Integration contains an unspecified vulnerability allowing unauthenticated network attackers to compromise Concurrent Processing, potentially enabling full system takeover.
Verdict
Today item, not a backlog item.
An unauthenticated remote attacker can exploit this vulnerability via HTTP to gain control of Oracle Concurrent Processing, a critical batch job execution component. Active exploitation and ransomware campaigns indicate immediate operational risk.
CISA KEV Yes · 2025-10-065Ransomware use Flagged5EPSS 0.99722 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
239 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-06), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99722 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Oracle, E-Business Suite. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I send a crafted HTTP request to the BI Publisher Integration endpoint without credentials.
Business
The organization's batch processing infrastructure becomes accessible to external threat actors.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the unspecified flaw to execute arbitrary operations within Concurrent Processing.
Business
Critical business processes dependent on scheduled jobs are disrupted or manipulated.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent control over the Concurrent Processing system to deploy ransomware or exfiltrate data.
Business
The organization faces operational shutdown, data loss, and potential ransom demands from coordinated threat campaigns.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05