# CVE-2021-46085: Privilege escalation in n/a

> Low-level administrators can delete high-level administrators, allowing unauthorized privilege escalation and data modification in OneBlog.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 25 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c74j-rm4q-qm76

## What is CVE-2021-46085?

CVE-2021-46085 is a medium-severity vulnerability in n/a, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OneBlog <= 2.2.8 is vulnerable to Insecure Permissions. Low level administrators can delete high-level administrators beyond their authority.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Oneblog Project Oneblog.

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

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

## Is CVE-2021-46085 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-46025](https://insights.sbomify.com/CVE-2021-46025/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46085 is a medium-severity vulnerability in n/a, published on 25 Jan 2022. 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-46085 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-46085/ (Markdown: https://insights.sbomify.com/CVE-2021-46085/index.md)
```

## Sources

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

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