dbcve.org
Personal CommunicationsApplication · Ibm

CVE-2025-1095

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
IBM Personal Communications v14 and v15 include a Windows service that is vulnerable to local privilege escalation (LPE). The vulnerability allows any interactively logged in users on the target computer to run commands with full privileges in the context of NT AUTHORITY\SYSTEM. This allows for a low privileged attacker to escalate their privileges. This vulnerability is due to an incomplete fix for CVE-2024-25029.

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

IBM Personal Communications v14 and v15 contains a Windows service vulnerable to local privilege escalation. The service runs with NT AUTHORITY\SYSTEM privileges and permits any interactively logged-in user to execute commands at SYSTEM level, allowing low-privileged users to escalate to full administrative privileges. This vulnerability stems from an incomplete fix for the prior CVE-2024-25029.

MitigationApply the vendor-supplied patch from IBM for Personal Communications v14 and v15. If patching is delayed, consider disabling the service or restricting interactive logon access until the update can be deployed.

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
Personal CommunicationsApplication
Affected:= 14.0.0= 15.0.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Verify IBM Personal Communications installation and version
    Check the installed version by examining the program's version information. On Windows, this can be done via Programs and Features, or by locating the main executable (typically in C:\Program Files\IBM\Personal Communications or similar) and viewing its file properties. Compare the version to 14.0.0 or 15.0.0.
    Affected if IBM Personal Communications version 14.0.0 or 15.0.0 is installed and the associated service is present.
  2. Identify the IBM Personal Communications Windows service
    Open Services console (services.msc) and look for services related to IBM Personal Communications, PCOMM, or IBM communications. The service name typically contains references to the product. Note the service name displayed.
    Affected if A service associated with IBM Personal Communications is found running on the system.
  3. Confirm the service runs with elevated privileges
    In Services console, right-click the identified IBM Personal Communications service, select Properties, and examine the 'Log On' tab. Verify if the service is configured to run as 'Local System' or 'NT AUTHORITY\SYSTEM'.
    Affected if The service Log On account is set to Local System or NT AUTHORITY\SYSTEM.
  4. Check if unprivileged users can interact with the service
    Examine the service's security descriptor permissions. Using sc queryex or msinfo32, identify if authenticated users or interactive logon users have permission to start, stop, or interact with the service. Specifically check if 'Interactive Users' or domain users have service control permissions.
    Affected if Non-administrative users (especially interactive/logged-on users) have permissions to control or interact with the SYSTEM-level service.

A user is affected if IBM Personal Communications version 14.0.0 or 15.0.0 is installed with a service running as NT AUTHORITY\SYSTEM that permits interactive or low-privileged users to execute commands at SYSTEM privilege level.

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 the vendor-supplied patch from IBM for Personal Communications v14 and v15. If patching is delayed, consider disabling the service or restricting interactive logon access until the update can be deployed.

Fix this in Personal Communications Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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