ScriptingApplication · Oracle

CVE-2025-61753

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-21

Fix available

A fix is available. Upgrade to after 12.2.14 or later.

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Vulnerability in the Oracle Scripting product of Oracle E-Business Suite (component: Miscellaneous). Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Scripting. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Scripting, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Scripting accessible data as well as unauthorized read access to a subset of Oracle Scripting accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Technical summary

dbcve analysis · high confidence

An injection-type vulnerability in Oracle E-Business Suite's Oracle Scripting component (versions 12.2.3-12.2.14) allows unauthenticated remote attackers via HTTP to achieve unauthorized read, insert, update, and delete access to a subset of accessible data. The attack requires human interaction and results in a scope change affecting additional products.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2025-61753 to the Oracle E-Business Suite environment. Restrict network access to Oracle Scripting interfaces where possible while awaiting the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ScriptingApplication

Affected:>= 12.2.3, <= 12.2.14

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Oracle E-Business Suite is installed

Review system inventory or check for Oracle application directories (typically under $ORACLE_HOME/apps) and verify the presence of EBS-related components.

Affected if Oracle E-Business Suite is present in the environment
Identify Oracle Scripting component version

Query the Oracle Scripting version through the EBS Administration interface, or check the version file in the Oracle Scripting installation directory. The version should be in the format 12.2.x.

Affected if The installed version is >= 12.2.3 and <= 12.2.14
Determine if Oracle Scripting HTTP listeners are enabled

Check the Oracle E-Business Suite concurrent manager configuration or HTTP server settings for the Oracle Scripting module (often accessible via /OA_HTML/oracle/scripts or similar paths). Review the HTTP port configuration in the EBS context file.

Affected if HTTP listeners for Oracle Scripting are active and accessible over the network
Verify network exposure of Oracle Scripting interfaces

Scan internal network ranges for open HTTP ports associated with the EBS instance (commonly ports 8000-8009, 9000-9090). Review firewall rules and load balancer configurations that expose EBS HTTP endpoints externally.

Affected if Oracle Scripting HTTP endpoints are reachable from untrusted networks or do not require authentication at the network layer

The environment is affected if Oracle E-Business Suite with Oracle Scripting version 12.2.3 through 12.2.14 is running and its HTTP interfaces are accessible, regardless of authentication configuration.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.14

Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for CVE-2025-61753 to the Oracle E-Business Suite environment. Restrict network access to Oracle Scripting interfaces where possible while awaiting the patch.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.15 or latest 12.2.x release

1. Identify the current Oracle E-Business Suite 12.2 Scripting version by navigating to the Oracle Application Manager and checking the version number.
2. Review the Oracle E-Business Suite 12.2.15 release notes or patch notes to confirm it includes the fix for CVE-2025-61753.
3. Download and apply Oracle E-Business Suite 12.2.15 or later from Oracle Support using the appropriate patch number (typically found in the Security Patch Update documentation).
4. After applying the patch, restart the Oracle Scripting services as required by the patch documentation.
5. Verify the fix by confirming the patch is applied and testing that the open redirect vulnerability is no longer exploitable.

Caveat Review Oracle's patch prerequisites and dependencies before applying; some patches may require interim patches or specific configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Scripting Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing12.0 h
Review / QA4.0 h

28.0 hours of engineering $4,760

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-61753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61753 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-61753?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to after 12.2.14 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Scripting

Remediation

Need this fixed?

Fix this in Scripting 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-61753 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References