# CVE-2021-26280: Permission bypass vulnerability in permission manager module

> A local application can bypass permission checks in the vivo permission manager to perform restricted system operations.

- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2024
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-gwhh-2295-5jfj

## What is CVE-2021-26280?

CVE-2021-26280 is a high-severity missing authorization vulnerability in vivo Permission manager module, published on 17 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Locally installed application can bypass the permission check and perform system operations that require permission.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2021-26280 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26280 is a high-severity missing authorization vulnerability in vivo Permission manager module, published on 17 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-26280 in the wild and no public exploit code.

Affected product: vivo Permission manager module. 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-26280/ (Markdown: https://insights.sbomify.com/CVE-2021-26280/index.md)
```

## Sources

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

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