{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15108 exists.","fix":"No fix has been published for CVE-2025-15108 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15108 is a medium-severity vulnerability in PandaXGO PandaX, published on 27 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-15108 and fix it if it is affected.\n\nWhat it is: CVE-2025-15108 is a medium-severity vulnerability in PandaXGO PandaX, published on 27 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-15108 exists.\n\nAffected product: PandaXGO PandaX. 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-2025-15108/ (Markdown: https://insights.sbomify.com/CVE-2025-15108/index.md)","id":"CVE-2025-15108","markdown":"https://insights.sbomify.com/CVE-2025-15108/index.md","name":"CVE-2025-15108","record":{"aliases":["GHSA-hj3q-q387-m5hr"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"PandaX web framework","requires_auth":"none","summary":"Attackers can exploit a hard-coded JWT secret in PandaX to bypass authentication and potentially take over accounts.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/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 vulnerability was detected in PandaXGO PandaX up to fb8ff40f7ce5dfebdf66306c6d85625061faf7e5. This affects an unknown function of the file config.yml of the component JWT Secret Handler. The manipulation of the argument key results in use of hard-coded cryptographic key\r . The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is reported as difficult. The exploit is now public and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. 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":"PandaXGO PandaX JWT Secret config.yml hard-coded key","id":"CVE-2025-15108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"jackq XCMS upload.php unrestricted upload","id":"CVE-2025-15109"},"packages":[],"prev":{"headline":"actiontech sqle JWT Secret jwt.go hard-coded key","id":"CVE-2025-15107"},"products":["PandaX"],"published":"2025-12-27","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["PandaXGO"]},"summary":"Attackers can exploit a hard-coded JWT secret in PandaX to bypass authentication and potentially take over accounts.","url":"https://insights.sbomify.com/CVE-2025-15108/"}