CVE-2025-5317
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 · uneditedAn improper access restriction to a folder in Bitdefender Endpoint Security Tools for Mac (BEST) before 7.20.52.200087 allows local users with administrative privileges to bypass the configured uninstall password protection. An unauthorized user with sudo privileges can manually remove the application directory (/Applications/Endpoint Security for Mac.app/) and the related directories within /Library/Bitdefender/AVP without needing the uninstall password.
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 confidenceThis is a local authorization bypass vulnerability in Bitdefender Endpoint Security Tools for Mac. The application's uninstall password protection can be circumvented by directly deleting the application files (/Applications/Endpoint Security for Mac.app/ and /Library/Bitdefender/AVP/*) using sudo privileges, bypassing the intended password-protected uninstallation mechanism.
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< 7.20.52.200087CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 Bitdefender Endpoint Security for Mac is installedCheck for the presence of /Applications/Endpoint Security for Mac.app/ directory using ls -la /Applications/ | grep -i endpointAffected if The application directory does not exist, meaning the product is not installed and this CVE does not apply.
-
Check installed version of Bitdefender Endpoint Security for MacRetrieve the installed version using the product's built-in mechanism or by reading version information from the application bundle in /Applications/Endpoint Security for Mac.app/Contents/Info.plistAffected if The installed version is lower than 7.20.52.200087, indicating the version is vulnerable to the authorization bypass.
-
Confirm the Bitdefender AVPSecurity daemon components existVerify the presence of /Library/Bitdefender/AVP/ directory contents using ls -la /Library/Bitdefender/AVP/Affected if The directory exists and contains application files, meaning the product is fully installed and the bypass could potentially be used to circumvent uninstall protection.
-
Compare your installed version to the affected rangeDocument the exact version number found and confirm it falls within the vulnerable range: any version < 7.20.52.200087Affected if The version number is 7.20.52.200087 or higher, the installation is not affected by this specific authorization bypass vulnerability.
You are affected if Bitdefender Endpoint Security for Mac is installed with a version lower than 7.20.52.200087, as the uninstall password protection can be bypassed by directly deleting the application files with elevated privileges.
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 · scoped7.20.52.200087
Upgrade to Bitdefender Endpoint Security Tools for Mac version 7.20.52.200087 or later. Until then, implement additional access controls via MDM or macOS restrictions to prevent unauthorized deletion of the application directories.
7.20.52.200087 or later
- 1. Check current installed version of Bitdefender Endpoint Security Tools for Mac by opening the application and navigating to About, or run: defaults read /Applications/Endpoint\ Security\ for\ Mac.app/Contents/Info CFBundleShortVersionString
- 2. If version is below 7.20.52.200087, download the fixed version from the Bitdefender official portal or your enterprise management console
- 3. Apply the upgrade using your organization's standard Bitdefender deployment method (e.g., Bitdefender GravityZone console for enterprises, or direct installer for standalone installations)
- 4. Restart the endpoint if required by the upgrade process
- 5. Verify the new version is installed: defaults read /Applications/Endpoint\ Security\ for\ Mac.app/Contents/Info CFBundleShortVersionString
- 6. Confirm the uninstall password protection is functioning correctly by attempting to access the removal directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5317 — 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-5317 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