dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-10672

HIGH · 7.8 CVSS v3.1 Published 2025-09-18
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
A vulnerability was found in whuan132 AIBattery up to 1.0.9. The affected element is an unknown function of the file AIBatteryHelper/XPC/BatteryXPCService.swift of the component com.collweb.AIBatteryHelper. The manipulation results in missing authentication. The attack requires a local approach. The exploit has been made public and could be used.

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

A missing authentication vulnerability exists in the BatteryXPCService XPC service component of the AIBattery app (com.collweb.AIBatteryHelper). The affected function in BatteryXPCService.swift lacks proper XPC connection validation, allowing any local process to invoke privileged operations without authentication checks.

MitigationUpdate to version 1.0.10 or later if available; otherwise, implement proper XPC connection validation (audit Mach service, verify calling process's code signature and bundle identifier) in the XPC service handler.

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 checks

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

  1. Verify AIBattery app installation
    Search for the app bundle with identifier com.collweb.AIBatteryHelper. On macOS, check /Applications or ~/Applications for AIBattery.app, or use 'lsappinfo' or 'mdfind' to locate the bundle.
    Affected if The app bundle com.collweb.AIBatteryHelper is found on the system
  2. Check installed version against fixed release
    Right-click AIBattery.app > Get Info, or run 'mdls -name CFBundleShortVersionString /path/to/AIBattery.app' to obtain the version number. Compare this to version 1.0.10.
    Affected if The installed version is lower than 1.0.10, or the version cannot be determined (older release)
  3. Locate BatteryXPCService XPC service
    Check for the XPC service binary within the app bundle (typically in Contents/XPCServices/), or search for the Mach service name. Use 'ls -la AIBattery.app/Contents/XPCServices/' and look for BatteryXPCService.xpc or similar. Also check for registered Mach services via 'launchctl list' or inspecting the app's Info.plist for XPCService entries.
    Affected if The BatteryXPCService.xpc or equivalent XPC service component exists within the AIBattery app bundle
  4. Inspect XPC service handler configuration
    Examine the XPC service's Info.plist (Contents/XPCServices/BatteryXPCService.xpc/Contents/Info.plist) for the XPCService key. Use 'plutil -p' to read the plist. Verify if the service exposes any privileged operations that lack connection validation.
    Affected if The BatteryXPCService is present and exposes callable methods without documented authentication requirements in the interface
  5. Check for Mach service registration
    Search system-wide Mach service registrations for entries related to AIBattery or BatteryXPCService. Examine /Library/LaunchDaemons/ or ~/Library/LaunchAgents/ for plist files matching 'AIBattery' or 'BatteryXPC'. Use 'grep -r AIBattery /Library/Launch*/' to find registered services.
    Affected if A Mach service associated with BatteryXPCService is registered and accessible system-wide

The system is affected if the AIBattery app (bundle com.collweb.AIBatteryHelper) is installed with a version prior to 1.0.10 and includes the BatteryXPCService XPC component, as the vulnerability allows unauthenticated local processes to invoke privileged operations.

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

Update to version 1.0.10 or later if available; otherwise, implement proper XPC connection validation (audit Mach service, verify calling process's code signature and bundle identifier) in the XPC service handler.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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