CVE-2025-56267
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 CSV injection vulnerability in the /id_profiles endpoint of Avigilon ACM v7.10.0.20 allows attackers to execute arbitrary code via suuplying a crafted Excel file.
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 confidenceA CSV injection vulnerability in the /id_profiles endpoint of Avigilon Access Control Manager v7.10.0.20 allows attackers to execute arbitrary code by supplying a crafted Excel file. The application appears to process spreadsheet data unsafely, potentially allowing formula injection that executes when the file is imported or viewed.
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.10.0.20CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Avigilon ACM installation versionCheck the installed version of Avigilon Access Control Manager in the system information, about page, or by querying the application's version endpoint. This is typically found in the ACM appliance management console or the software itself.Affected if The installed version is Avigilon Access Control Manager v7.10.0.20 specifically, or if the version cannot be determined but the product is confirmed as Avigilon ACM.
-
Locate the /id_profiles endpointCheck if the /id_profiles endpoint is exposed on the Avigilon ACM web interface or API. This is typically found under the identity or user profile management section of the ACM system.Affected if The /id_profiles endpoint exists and is accessible on the Avigilon ACM instance.
-
Verify CSV/Excel export capabilityAttempt to export data from the id_profiles section. Look for export buttons, CSV download options, or API endpoints that generate Excel spreadsheet files from identity profile data.Affected if The system allows exporting identity profile data to CSV or Excel file formats through the /id_profiles functionality.
-
Check for formula character handling in exportsExport a test identity profile to CSV/Excel and inspect the output file. Open the file in a spreadsheet application to observe if fields containing formula characters (=, +, -, @) are handled or neutralized.Affected if The exported file contains raw data without sanitization of formula characters, meaning fields with =, +, -, @, tab, or CR characters are written as-is.
A system is affected if it runs Avigilon Access Control Manager version 7.10.0.20, has the /id_profiles endpoint accessible, and supports CSV/Excel export of identity profiles without sanitizing formula characters in the exported data.
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.
From vendor dataRestrict network access to the /id_profiles endpoint, implement strict input validation and sanitization on file imports, and disable or sandbox Excel formula execution in the application's file processing pipeline. Contact Avigilon for a patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56267 — 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-56267 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