# CVE-2026-86241: liufee FeehiCMS Cookie Validation main-local.php hard-coded key

> Attackers can bypass cookie validation in FeehiCMS due to a hard-coded cryptographic key, potentially leading to session hijacking or unauthorized access.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-pqpw-2pq6-37xx

## What is CVE-2026-86241?

CVE-2026-86241 is a medium-severity vulnerability in liufee FeehiCMS, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in liufee FeehiCMS up to 2.1.1. This impacts an unknown function of the file environments/prod/backend/config/main-local.php of the component Cookie Validation. This manipulation of the argument cookieValidationKey causes use of hard-coded cryptographic key
 . The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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


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

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

## Is CVE-2026-86241 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86241 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86241 is a medium-severity vulnerability in liufee FeehiCMS, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86241 exists.

Affected product: liufee FeehiCMS. 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-86241/ (Markdown: https://insights.sbomify.com/CVE-2026-86241/index.md)
```

## Sources

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

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