dbcve.org
Communications Order And Service ManagementApplication · Oracle

CVE-2025-21542

MEDIUM · 6.3 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Communications Order and Service Management product of Oracle Communications Applications (component: Security). Supported versions that are affected are 7.4.0, 7.4.1 and 7.5.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Communications Order and Service Management. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Order and Service Management accessible data as well as unauthorized read access to a subset of Oracle Communications Order and Service Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Communications Order and Service Management. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

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 · moderate confidence

HTTP-based vulnerability in the Security component of Oracle Communications Order and Service Management (versions 7.4.0-7.5.0) allows low-privileged attackers with network access to achieve unauthorized read and write access to a subset of data, plus partial denial of service. The CVSS vector indicates a broken access control scenario with low complexity, low privilege requirements, and no user interaction needed.

MitigationApply the Oracle patch or upgrade to a fixed version beyond 7.5.0. If patches are unavailable, restrict network access to the management interface and implement additional access controls until the vendor fix is available.

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
Communications Order And Service ManagementApplication
Affected:= 7.4.0= 7.4.1= 7.5.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify installed version of Oracle Communications Order and Service Management
    Locate the product installation directory and check version files, or query the management interface for version information. Common locations include installation logs, version.properties files, or the admin console.
    Affected if The installed version matches 7.4.0, 7.4.1, or 7.5.0 exactly.
  2. Determine if HTTP-based management interface is network-accessible
    Attempt to reach the OSM management ports (typically 7001, 7002, or configured custom ports) from a non-localhost network address using curl or a browser. Check firewall rules and reverse proxy configurations.
    Affected if The HTTP management interface is reachable from network addresses other than localhost/localhost-only binding.
  3. Verify access control configuration for the Security component
    Inspect the WebLogic or Oracle Fusion Middleware security configuration files (typically in config.xml or within the WebLogic console) for the OSM application. Check for proper role-based access control (RBAC) enforcement on security-related endpoints.
    Affected if The Security component allows unauthenticated or low-privileged network access to sensitive operations.
  4. Check for unauthenticated HTTP endpoints exposure
    Review the deployed web application descriptors (web.xml) and any custom security filter mappings. Test known security-sensitive URLs without providing credentials to verify if they are accessible.
    Affected if HTTP endpoints related to Security component functionality are accessible without proper authentication.

You are affected if Oracle Communications Order and Service Management version 7.4.0, 7.4.1, or 7.5.0 is installed AND the HTTP management interface is network-accessible, allowing unauthorized access to Security component functions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle patch or upgrade to a fixed version beyond 7.5.0. If patches are unavailable, restrict network access to the management interface and implement additional access controls until the vendor fix is available.

Recommended fix Moderate confidence

Oracle Communications Order and Service Management 7.5.1 or later (apply Oracle Critical Patch Update containing fix for CVE-2025-21542)

  1. 1. Navigate to Oracle Support (support.oracle.com) and search for CVE-2025-21542 or the Oracle Communications Order and Service Management (OSM) Critical Patch Update.
  2. 2. Download the appropriate patch for your specific version (7.4.0, 7.4.1, or 7.5.0) as identified in the Oracle Critical Patch Update advisory.
  3. 3. Review the patch README file for any pre-installation requirements or prerequisites.
  4. 4. Back up your current Oracle Communications Order and Service Management installation and database.
  5. 5. Apply the patch following Oracle's standard patch application process (typically using OPatch or the installer provided with the patch).
  6. 6. Verify the patch was applied successfully by checking the patch inventory and confirming the CVE is resolved.
Caveat Consult Oracle patch README for any known issues or post-install configuration requirements; test thoroughly in non-production environment before applying to production

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

Fix this in Communications Order And Service Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21542 — 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-21542 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