Improper Privilege ManagementWeakness · CWE-269

CVE-2024-1973

HIGH · 8.5 CVSS v3.1 Published 2024-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
By leveraging the vulnerability, lower-privileged users of Content Manager can manipulate Content Manager clients to elevate privileges and perform unauthorized operations.

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

This is a privilege escalation vulnerability in OpenText Content Manager where lower-privileged users can manipulate Content Manager clients to elevate their privileges and perform unauthorized operations. The vulnerability allows authenticated users with limited permissions to bypass access controls and gain higher-level access to the system.

MitigationApply vendor patches or security updates for Content Manager. Until a patch is available, implement strict role-based access controls and monitor for unauthorized privilege escalation attempts.

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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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 checks

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

  1. Identify OpenText Content Manager installation
    Check for Content Manager server components and client installations. Look for processes named 'TRIM', 'HP CM', or 'OpenText CM' in running services, or check installation directories like C:\Program Files\OpenText\Content Manager or /opt/opentext/cm. Check Windows Registry under HKLM\SOFTWARE\OpenText for Content Manager entries.
    Affected if OpenText Content Manager software is present on the system
  2. Determine installed version
    Run 'About' or version check in Content Manager admin console, check installer history, or query the CM server for its version string via admin interface or installed program details.
    Affected if Any version of OpenText Content Manager is installed (version range not specified in CVE data)
  3. Review user role assignments
    Access Content Manager administration console and enumerate all user accounts and their assigned roles. Identify users with limited or restricted permission sets - these are the accounts that could potentially be exploited.
    Affected if There are authenticated users with limited permissions in the system
  4. Examine access control configuration
    Inspect Content Manager security settings, particularly role-based access control (RBAC) configurations. Check for custom roles, permission overrides, or access control lists that govern client operations and file handling.
    Affected if Role-based access controls are configured (the vulnerability allows bypassing these)
  5. Review audit and security logs
    Search Content Manager audit logs for events involving permission changes, role modifications, or operations performed by low-privilege users that exceed their assigned access level. Look for unexpected admin actions from standard user accounts.
    Affected if Audit logs show operations by limited-permission users that bypass normal access controls

A user is affected if OpenText Content Manager is installed and there are authenticated users with limited permissions, since the vulnerability allows such users to escalate privileges and bypass access controls.

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

Apply vendor patches or security updates for Content Manager. Until a patch is available, implement strict role-based access controls and monitor for unauthorized privilege escalation attempts.

Have this fixed 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-2024-1973 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1973 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