dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-3272

MEDIUM · 6.7 CVSS v4.0 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Incorrect Authorization vulnerability in OpenText™ Operations Bridge Manager.  The vulnerability could allow authenticated users to change their password without providing their old password. This issue affects Operations Bridge Manager: 24.2, 24.4.

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

This is an incorrect authorization vulnerability in OpenText Operations Bridge Manager where authenticated users can change their own password without providing their current password. The password change function lacks proper authorization validation to verify the user's identity before allowing the modification.

MitigationImplement proper authorization checks requiring the current password validation before allowing any password change operation. This ensures only the legitimate password owner can modify their credentials.

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

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
Local
Complexity
Low
Privileges
None
Authentication
None
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:L/U:Green

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. Confirm OpenText Operations Bridge Manager installation
    Locate the OBM installation directory and check for version information in product metadata, license files, or the application's about/version page. Common locations include /opt/otobo or C:\Program Files\OpenText\OperationsBridgeManager
    Affected if OBM is installed and running
  2. Identify the installed OBM version
    Use the product's version check mechanism - typically via the admin console, version.sh/verson.bat script in the installation directory, or the application's help/about section
    Affected if Version cannot be determined or is within the affected range
  3. Verify password change function accessibility
    Locate the password change interface in the OBM web console or admin panel. Check if the endpoint for password modification (typically /user/password or similar) is exposed and accessible to authenticated users
    Affected if Password change functionality is exposed to authenticated users without additional authorization checks
  4. Inspect password change authorization logic
    Examine the backend configuration or application logs for the password change operation. Look for configuration parameters that control whether current password validation is required before allowing a password modification
    Affected if Configuration shows no requirement for current password validation before password change
  5. Check user authorization enforcement
    Review the authentication and authorization settings in the OBM security configuration. Verify if the password change operation validates user identity beyond mere session authentication
    Affected if Authorization enforcement is missing or disabled for password modification

The environment is affected if OpenText Operations Bridge Manager is running and the password change function allows modifications without validating the user's current password.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks requiring the current password validation before allowing any password change operation. This ensures only the legitimate password owner can modify their credentials.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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