{"answers":{"affected":"2 open source packages ship an affected version, including feehi/feehicms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63523 exists.","fix":"No fix has been published for CVE-2025-63523 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63523 is a medium-severity vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-63523 and fix it if it is affected.\n\nWhat it is: CVE-2025-63523 is a medium-severity vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63523 exists.\n\nAffected packages and fixed versions:\n- feehi/feehicms (Packagist): affected all versions; no fix listed\n- feehi/feehicms (Packagist): affected all versions; no fix listed\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-2025-63523/ (Markdown: https://insights.sbomify.com/CVE-2025-63523/index.md)","id":"CVE-2025-63523","markdown":"https://insights.sbomify.com/CVE-2025-63523/index.md","name":"CVE-2025-63523","record":{"aliases":["GHSA-qgc9-p7cj-jvh6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"FeehiCMS","requires_auth":"none","summary":"An authenticated attacker can modify read-only parameters to change usernames, compromising data integrity in FeehiCMS.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"feehicms","vendor":"feehi"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"FeehiCMS version 2.1.1 fails to enforce server-side immutability for parameters that are presented to clients as \"read-only.\" An authenticated attacker can intercept and modify the parameter in transit and the backend accepts the changes. This can lead to unintended username changes.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FeehiCMS fails to enforce server-side immutability","id":"CVE-2025-63523","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2025-63525"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"feehi/feehicms","purl":null,"source":"GHSA-qgc9-p7cj-jvh6"},{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"feehi/feehicms","purl":"pkg:composer/feehi/feehicms","source":"GHSA-qgc9-p7cj-jvh6"}],"prev":{"headline":"FeehiCMS is vulnerable to reverse tabnabbing","id":"CVE-2025-63522"},"products":["n/a"],"published":"2025-12-01","related":[{"cvss_score":9.8,"headline":"liufee CMS File Upload vulnerability","id":"CVE-2020-21174","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":9.8,"headline":"Liufee CMS File Upload vulnerability","id":"CVE-2020-21489","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":9.8,"headline":"FeehiCMS has an arbitrary file upload vulnerability","id":"CVE-2020-21516","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":9.8,"headline":"Arbitrary Code Execution in feehi/cms","id":"CVE-2020-21322","kev_date_added":null,"published":"2021-09-15"},{"cvss_score":6.9,"headline":"FeehiCMS TimThumb timthumb.php server-side request forgery","id":"CVE-2025-15264","kev_date_added":null,"published":"2025-12-30"},{"cvss_score":6.5,"headline":"FeehiCMS Has a Remote Code Execution via Unrestricted File Upload in Ad Management","id":"CVE-2025-65657","kev_date_added":null,"published":"2025-12-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-01","vendors":["n/a"]},"summary":"An authenticated attacker can modify read-only parameters to change usernames, compromising data integrity in FeehiCMS.","url":"https://insights.sbomify.com/CVE-2025-63523/"}