CVE-2025-0396
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 · uneditedA vulnerability, which was classified as critical, has been found in exelban stats up to 2.11.21. This issue affects the function shouldAcceptNewConnection of the component XPC Service. The manipulation leads to command injection. It is possible to launch the attack on the local host. Upgrading to version 2.11.22 is able to address this issue. It is recommended to upgrade the affected component.
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 confidenceA command injection vulnerability exists in the XPC Service component of exelban stats (a macOS system monitoring tool). The shouldAcceptNewConnection function fails to properly sanitize inputs, allowing a local attacker to execute arbitrary commands. The vulnerability is locally exploitable and rated 7.8 (HIGH) due to the potential for local privilege escalation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify exelban stats is installedOpen Terminal and run: ls /Applications | grep -i stats or check System Settings > Privacy & Security > Login Items for 'stats'Affected if The application exists in /Applications or appears in Login Items
-
Determine installed versionRun: defaults read /Applications/stats.app/Contents/Info.plist CFBundleShortVersionString or right-click stats.app > Get Info > VersionAffected if Version is lower than 2.11.22 (the fixed release)
-
Confirm XPC Service component is presentRun: ls /Applications/stats.app/Contents/XPCServices/ 2>/dev/null || echo 'No XPCServices folder found'Affected if An XPC Service bundle exists within the application bundle (the vulnerable component is present)
-
Check if stats daemon is runningRun: ps aux | grep -i stats | grep -v grepAffected if The stats daemon process is active, meaning the XPC Service listener is enabled and potentially exploitable
You are affected if exelban stats versions below 2.11.22 are installed and the XPC Service daemon is running, as the shouldAcceptNewConnection function in that component accepts unsanitized input.
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 · scopedUpgrade exelban stats to version 2.11.22 or later to address the command injection vulnerability in the XPC Service component.
2.11.22
- 1. Identify the exelban stats installation on the system
- 2. Backup the current installation and any associated data
- 3. Upgrade exelban stats to version 2.11.22
- 4. Restart the XPC Service to ensure the patched version is loaded
- 5. Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0396 — 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-0396 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