{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86241 exists.","fix":"No fix has been published for CVE-2026-86241 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-86241 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86241 exists.\n\nAffected product: liufee FeehiCMS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-86241/ (Markdown: https://insights.sbomify.com/CVE-2026-86241/index.md)","id":"CVE-2026-86241","markdown":"https://insights.sbomify.com/CVE-2026-86241/index.md","name":"CVE-2026-86241","record":{"aliases":["GHSA-pqpw-2pq6-37xx"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FeehiCMS","requires_auth":"none","summary":"Attackers can bypass cookie validation in FeehiCMS due to a hard-coded cryptographic key, potentially leading to session hijacking or unauthorized access.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"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\r . 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"liufee FeehiCMS Cookie Validation main-local.php hard-coded key","id":"CVE-2026-86241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Unauthenticated RCE via Custom Plugin HTTP Path on Dynamically Linked Builds","id":"CVE-2026-86242"},"packages":[],"prev":{"headline":"liufee FeehiCMS UEditor Uploader.php catchImage server-side request forgery","id":"CVE-2026-86240"},"products":["FeehiCMS"],"published":"2026-09-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-11","vendors":["liufee"]},"summary":"Attackers can bypass cookie validation in FeehiCMS due to a hard-coded cryptographic key, potentially leading to session hijacking or unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-86241/"}