CVE-2025-21544
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 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 require human interaction from a person other than the attacker and while the vulnerability is in Oracle Communications Order and Service Management, 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 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. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · moderate confidenceInsufficient technical details provided in the CVE description. The vulnerability is in the Security component of Oracle Communications Order and Service Management versions 7.4.0-7.5.0, allowing low-privileged attackers with network access to achieve unauthorized read access to a subset of data and unauthorized update/insert/delete access to some data. Requires user interaction from a person other than the attacker. The scope change indicates attacks may impact additional products beyond the targeted system.
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= 7.4.0= 7.4.1= 7.5.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle Communications Order and Service Management is installedLook for the OSM installation directory or check for OSM-related processes/services on the server. Common locations include Oracle Middleware home directories. On Linux, run: ps -ef | grep -i osm or check for OSM-related processes. On Windows, check Services for Oracle Communications Order and Service Management.Affected if The product is present on the system.
-
Determine the installed OSM versionCheck the version of Oracle Communications Order and Service Management. This can typically be found in the product's About or version file, often in the installation directory or via the OSM administration console. Check files like version.txt, or look in the Oracle_MW_HOME/osm directory. The command line might include: $ORACLE_HOME/bin/osmVersion or similar version retrieval utility.Affected if The installed version matches 7.4.0, 7.4.1, or 7.5.0.
-
Verify network accessibility of the OSM interfaceDetermine if the OSM web interface or API endpoints are accessible from the network. Check firewall rules, load balancer configurations, and the OSM server's network bindings. Look for exposed ports typically used by OSM (often 7001-7010 range for WebLogic). Run: netstat -an | grep LISTEN | grep -E '700[0-9]|8010|8080' to identify listening HTTP ports.Affected if The OSM interface is reachable from untrusted networks.
-
Check for existing user accounts and low-privileged accessReview the OSM user directory or identity store to identify accounts with low privileges. This can be done through the OSM Administration console under User Management, or by checking the underlying LDAP/WebLogic security realm. Verify if low-privileged accounts exist that could be leveraged by an attacker.Affected if Low-privileged OSM user accounts exist that could be compromised.
The environment is affected if Oracle Communications Order and Service Management versions 7.4.0, 7.4.1, or 7.5.0 are installed AND the OSM interface is network-accessible to untrusted users.
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's available security patches for the affected versions (7.4.0, 7.4.1, 7.5.0). Until a patch is available, restrict network access to the Order and Service Management interface to trusted users only and monitor for suspicious activity.
Upgrade to the latest available version of Oracle Communications Order and Service Management (consult Oracle's software configuration guide for the successor version to 7.5.0)
- 1. Review the Oracle Critical Patch Update advisory for January 2025 (or the applicable CPU) to obtain the specific patch for CVE-2025-21544
- 2. Download the patch from Oracle Support (patch number will be listed in the CPU advisory)
- 3. Apply the patch following Oracle's standard patch application procedure for Oracle Communications Order and Service Management
- 4. After patching, verify the fix by confirming the patch is applied and testing the security boundary affected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21544 — 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-21544 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