CVE-2025-53072
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.
NVD · uneditedVulnerability in the Oracle Marketing product of Oracle E-Business Suite (component: Marketing Administration). 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 Marketing. Successful attacks of this vulnerability can result in takeover of Oracle Marketing. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
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.
dbcve analysis · high confidenceUnauthenticated remote code execution vulnerability in Oracle E-Business Suite Marketing Administration component allowing complete system takeover via HTTP. The CVSS vector indicates network-accessible exploitation with no authentication required and full confidentiality, integrity, and availability impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE data>= 12.2.3, <= 12.2.14CVSS 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.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle E-Business Suite is installedCheck for Oracle E-Business Suite installation directories or running processes (such as oacore, forms, apache) on the server. Look for ORACLE_HOME environment variable pointing to EBS directories.Affected if Oracle E-Business Suite is present and running on the network.
-
Identify Oracle Marketing module versionQuery the Oracle Applications Manager (OAM) or use the command 'adident Header $OA_META/filename' on Marketing-related JAR files in the EBS Oracle Home. The version is also visible in the About Oracle E-Business Suite page accessible via the /OA_HTML/AboutOracleEBS.html endpoint.Affected if The installed version falls within >= 12.2.3 and <= 12.2.14.
-
Verify Marketing Administration component is exposedCheck if the Oracle Marketing Administration interface is accessible over HTTP/HTTPS from the network. Test access to common Marketing-related URLs such as /OA_HTML/marketing or /oa_servlets/marketing. Review web server configuration files (httpd.conf, Oracle HTTP Server config) for exposed Marketing paths.Affected if The Marketing Administration component is network-accessible without authentication.
-
Inspect access logs for suspicious Marketing endpoint activityReview Apache/OHS access logs (default location $ORACLE_HOME/Apache/Apache/logs/access_log) and Oracle E-Business Suite logs for unusual requests to Marketing Administration URLs, especially those containing encoded payloads, SQL injection patterns, or unexpected HTTP methods.Affected if Log entries show unauthorized or suspicious requests to Marketing Administration endpoints.
The environment is affected if Oracle E-Business Suite with Oracle Marketing version 12.2.3 through 12.2.14 has its Marketing Administration component network-accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply Oracle Critical Patch Update immediately; restrict network access to Oracle Marketing endpoints until patch is applied; validate that unauthorized access has not already occurred.
- Check Oracle My Oracle Support (MOS) for the latest Critical Patch Update (CPU) that addresses CVE-2025-53072
- Review Oracle E-Business Suite 12.2 release documentation and patching guidelines
- Apply the appropriate Oracle E-Business Suite patch from Oracle's official CPU release
- After patching, verify the Marketing Administration component no longer accepts unauthenticated HTTP requests
- Confirm the patch was applied successfully by checking the applied patches in ADADMIN or similar utility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53072 in production — separate from our analysis above.
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.
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.
- 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