# CVE-2026-95263: Privilege escalation in n/a

> A low-privilege administrator can reset the super administrator password without the old password, leading to full account takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-p8wc-cj6h-9g96

## What is CVE-2026-95263?

CVE-2026-95263 is a high-severity vulnerability in n/a, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Feehi CMS 2.1.1 is vulnerable to Incorrect Access Control. A low-privilege backend administrator with administrator-update permission can change the password of the built-in super administrator account. The server does not enforce protection for this account, and the update scenario does not require the old password.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-95263?


## How do I fix CVE-2026-95263?

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

## Is CVE-2026-95263 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95263 and fix it if it is affected.

What it is: CVE-2026-95263 is a high-severity vulnerability in n/a, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95263 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-2026-95263/ (Markdown: https://insights.sbomify.com/CVE-2026-95263/index.md)
```

## Sources

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

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