dbcve.org
Applications ManagerApplication · Oracle

CVE-2025-53058

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 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 · unedited
Vulnerability in the Oracle Applications Manager product of Oracle E-Business Suite (component: Application Logging Interfaces). 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 Applications Manager. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications Manager, 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 Applications Manager accessible data as well as unauthorized read access to a subset of Oracle Applications Manager 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 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 confidence

Unauthenticated HTTP vulnerability in Oracle Applications Manager's Application Logging Interfaces component (versions 12.2.3-12.2.14) allows remote attackers to read, insert, update, or delete a subset of application data without credentials, requiring human interaction to trigger.

MitigationApply Oracle's latest security patches for E-Business Suite 12.2.3-12.2.14; meanwhile, restrict network access to Oracle Applications Manager interfaces and monitor for suspicious logging activity.

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
Applications ManagerApplication
Affected:>= 12.2.3, <= 12.2.14

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.

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? 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 checks

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

  1. Verify Oracle Applications Manager version
    Use Oracle E-Business Suite administrative utilities or query the version information schema to determine the installed Oracle Applications Manager version
    Affected if Installed version falls within the range 12.2.3 to 12.2.14 inclusive
  2. Confirm Application Logging Interfaces component status
    Check the Oracle Applications Manager configuration to verify whether the Application Logging Interfaces component is deployed and enabled
    Affected if Application Logging Interfaces component is present and enabled
  3. Inspect HTTP endpoint exposure
    Review Oracle HTTP Server or Oracle WebLogic configuration to determine if the Application Logging Interfaces are accessible via unauthenticated HTTP endpoints
    Affected if Unauthenticated HTTP access to Application Logging Interfaces is permitted on the network
  4. Audit logging activity for anomalies
    Examine Oracle Applications Manager audit logs and logging interface access records for unexpected read, insert, update, or delete operations
    Affected if Suspicious or unauthorized data operations appear in the logging interface audit trail

User is affected if running Oracle Applications Manager version 12.2.3-12.2.14 with the Application Logging Interfaces component enabled and exposed to unauthenticated HTTP access

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 12.2.14
Interim mitigation

Apply Oracle's latest security patches for E-Business Suite 12.2.3-12.2.14; meanwhile, restrict network access to Oracle Applications Manager interfaces and monitor for suspicious logging activity.

Recommended fix Moderate confidence

Upgrade to Applications Manager version 12.2.15 or later, or apply the relevant CPU patch (consult Oracle CPU advisory for specific patch number)

  1. Check Oracle's official Critical Patch Update (CPU) advisory for October 2025 or later to identify the specific patch number for this CVE
  2. Apply the latest Oracle E-Business Suite CPU that includes the fix for CVE-2025-53058
  3. Alternatively, upgrade Applications Manager to a version newer than 12.2.14 (e.g., 12.2.15 or later)
  4. After applying the patch or upgrade, verify the fix by reviewing the Oracle CPU documentation
Caveat Oracle E-Business Suite upgrades may require regression testing of custom integrations and should be performed in a non-production environment first

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

Fix this in Applications Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53058 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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