# CVE-2021-43563: Missing authorization in n/a

> Unauthenticated attackers can bypass access controls to download media files from the DAM system via the pixx.io API.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 10 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5j5p-cr5c-763j

## What is CVE-2021-43563?

CVE-2021-43563 is a high-severity missing authorization vulnerability in n/a, published on 10 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the pixxio (aka pixx.io integration or DAM) extension before 1.0.6 for TYPO3. The Access Control in the bundled media browser is broken, which allows an unauthenticated attacker to perform requests to the pixx.io API for the configured API user. This allows an attacker to download various media files from the DAM system.

## Which versions are affected by CVE-2021-43563?

It affects 1 product.


Products: Pixxio Pixx.io.

## How do I fix CVE-2021-43563?

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

## Is CVE-2021-43563 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43562](https://insights.sbomify.com/CVE-2021-43562/): Server-side request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43563 and fix it if it is affected.

What it is: CVE-2021-43563 is a high-severity missing authorization vulnerability in n/a, published on 10 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43563 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-2021-43563/ (Markdown: https://insights.sbomify.com/CVE-2021-43563/index.md)
```

## Sources

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

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