dbcve.org
LiveApplication · Asseco

CVE-2025-66955

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Local File Inclusion in Contact Plan, E-Mail, SMS and Fax components in Asseco SEE Live 2.0 allows remote authenticated users to access files on the host via "path" parameter in the downloadAttachment and downloadAttachmentFromPath API calls.

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 confidence

Local File Inclusion vulnerability in Asseco SEE Live 2.0 allows remote authenticated users to access arbitrary files on the host via the 'path' parameter in downloadAttachment and downloadAttachmentFromPath API calls within Contact Plan, E-Mail, SMS, and Fax components.

MitigationImplement strict input validation and path allowlisting on the 'path' parameter; restrict API access to authorized users only and apply vendor patches when available.

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
LiveApplication
Affected:= 2.0

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify Asseco Live 2.0 installation
    Locate the application installation directory or check the web interface for version information. Common paths may include /opt/asseco-live, /var/www/asseco, or consult system inventory/CMDB for the application.
    Affected if The installed version is Asseco Live 2.0 exactly.
  2. Confirm API endpoints are accessible
    Check if the application exposes API endpoints for downloadAttachment or downloadAttachmentFromPath. These are typically found under /api/contacts, /api/email, /api/sms, or /api/fax paths. Inspect the application's routing configuration or web server logs for these endpoints.
    Affected if The downloadAttachment or downloadAttachmentFromPath API endpoints are reachable without being explicitly disabled.
  3. Verify authentication is required for the API
    Review the application's access control configuration to confirm that the vulnerable endpoints require valid authentication. Check if anonymous access is permitted to the Contact Plan, E-Mail, SMS, or Fax API components.
    Affected if The API endpoints are accessible to unauthenticated users or users without proper role-based access to the affected components.
  4. Inspect path parameter handling
    Examine the application's request handling for the 'path' parameter in the affected API calls. Review any path traversal validation logic in the application configuration or middleware.
    Affected if The application does not perform strict validation or allowlisting on the 'path' parameter, permitting directory traversal sequences like ../
  5. Check API access controls for Contact Plan, E-Mail, SMS, and Fax
    Review the role-based access control (RBAC) or permission settings for each affected component. Verify whether all authenticated users have access to downloadAttachment functions or if access is restricted to authorized roles only.
    Affected if Authenticated users with basic access can invoke downloadAttachment or downloadAttachmentFromPath in any of the four affected components.

You are affected if Asseco Live 2.0 is running and the downloadAttachment/downloadAttachmentFromPath APIs in Contact Plan, E-Mail, SMS, or Fax components are accessible to authenticated users without strict path allowlisting on the 'path' parameter.

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

Implement strict input validation and path allowlisting on the 'path' parameter; restrict API access to authorized users only and apply vendor patches when available.

Fix this in Live Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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