{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8739 exists.","fix":"No fix has been published for CVE-2026-8739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8739 is a medium-severity vulnerability in Sanluan PublicCMS, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8739 and fix it if it is affected.\n\nWhat it is: CVE-2026-8739 is a medium-severity vulnerability in Sanluan PublicCMS, published on 17 May 2026. 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-2026-8739 exists.\n\nAffected product: Sanluan PublicCMS. 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-8739/ (Markdown: https://insights.sbomify.com/CVE-2026-8739/index.md)","id":"CVE-2026-8739","markdown":"https://insights.sbomify.com/CVE-2026-8739/index.md","name":"CVE-2026-8739","record":{"aliases":["GHSA-2352-54f8-q7h5"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PublicCMS","requires_auth":"none","summary":"Remote attackers can exploit a hard-coded cryptographic key in PublicCMS to bypass security mechanisms, as the vendor has not provided a fix.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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 Sanluan PublicCMS 5.202506.d. The affected element is the function getSignKey of the file publiccms-core/src/main/java/com/publiccms/logic/component/config/SafeConfigComponent.java. The manipulation of the argument privatefile_key results in use of hard-coded cryptographic key\r . The attack can be executed remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Sanluan PublicCMS SafeConfigComponent.java getSignKey hard-coded key","id":"CVE-2026-8739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Sanluan PublicCMS templateResult API TemplateResultDirective.java execute special elements used in a template engine","id":"CVE-2026-8740"},"packages":[],"prev":{"headline":"Sanluan PublicCMS Trade Payment Flow TradeOrderController.java AccountGatewayComponent.pay logic error","id":"CVE-2026-8738"},"products":["PublicCMS"],"published":"2026-05-17","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-05-18","vendors":["Sanluan"]},"summary":"Remote attackers can exploit a hard-coded cryptographic key in PublicCMS to bypass security mechanisms, as the vendor has not provided a fix.","url":"https://insights.sbomify.com/CVE-2026-8739/"}