# CVE-2025-66956: Missing authorization in n/a

> Remote attackers can access and execute attachments in Asseco SEE Live components via computable URLs due to insecure access control.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-798g-p7qc-9jv4

## What is CVE-2025-66956?

CVE-2025-66956 is a critical missing authorization vulnerability in n/a, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure Access Control in Contact Plan, E-Mail, SMS and Fax components in Asseco SEE Live 2.0 allows remote attackers to access and execute attachments via a computable URL.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-66956?


## How do I fix CVE-2025-66956?

No fix has been published for CVE-2025-66956 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-66956 being exploited?

There is no known exploitation of CVE-2025-66956 in the wild and no public exploit code.

Public exploit code:

- Insecure Access Control in Contact Plan, E-Mail, SMS and Fax components in Asseco SEE Live 2.0 allows remote attackers to access and execute attachments via a computable URL. (github_poc): https://github.com/TheWoodenBench/CVE-2025-66956

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66956 and fix it if it is affected.

What it is: CVE-2025-66956 is a critical missing authorization vulnerability in n/a, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66956 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-66956/ (Markdown: https://insights.sbomify.com/CVE-2025-66956/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-66956
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-66956
- OSV: https://osv.dev/vulnerability/CVE-2025-66956

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-66956/
Summaries are generated and may contain mistakes; the official description above is the record.