CVE Tools

CVE-2025-35981

No known exploitation. EPSS puts it in the 2nd percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record
  1. Check your Command Centre Server version and see if it is one of: 9.30.1874 (MR1), 9.20.2337 (MR3), or 9.10.3194 (MR6).
  2. If you are on one of those versions, immediately restrict “Operator” privileges to only the people who truly need them.
  3. Review and tighten internal permissions around who can view cardholder-related personal data in Command Centre Server.
  4. Contact your software vendor or support team to ask whether a patch is available for CVE-2025-35981 and request the earliest fixed version for your exact release.
  5. Increase monitoring of operator activity (especially any viewing of cardholder details) and retain logs for internal review.

What it is

From the CVE record

Exposure of Private Personal Information to an Unauthorized Actor (CWE-359) in the Command Centre Server allows a privileged Operator to view limited personal data about a Cardholder they would not normally have permissions to view. This issue affects Command Centre Server: 9.30.1874 (MR1), 9.20.2337 (MR3), 9.10.3194 (MR6).

In plain language

Written by AI from the record

CVE-2025-35981 is a privacy flaw in Command Centre Server where certain privileged operators may be able to see limited cardholder personal information they normally shouldn’t—most small businesses should treat this as a low-to-medium concern unless you have roles with operator privileges.

CWE-359 private data exposure in Command Centre Server allows a privileged Operator to view limited personal data about a Cardholder outside their intended authorization boundaries (unauthorized authorization to view cardholder details).

If you're affected

  • Limited cardholder privacy exposure
  • Unauthorized internal access risk
  • Regulatory/privacy compliance risk
  • Trust and reputational harm

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS2nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.1% chance of exploitation activity in the next 30 days, which ranks it in the 2nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

3 events over 4 days, from the signal feeds we watch.

  1. Record updated
  2. Publishedweakness classified

Affected products

Technical detail

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

Scored 5.5 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Command Centre Server, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store