{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67504 exists.","fix":"No fix has been published for CVE-2025-67504 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67504 is a critical vulnerability in WBCE_CMS, published on 9 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-67504 and fix it if it is affected.\n\nWhat it is: CVE-2025-67504 is a critical vulnerability in WBCE_CMS, published on 9 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-67504 exists.\n\nAffected product: WBCE_CMS. 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-67504/ (Markdown: https://insights.sbomify.com/CVE-2025-67504/index.md)","id":"CVE-2025-67504","markdown":"https://insights.sbomify.com/CVE-2025-67504/index.md","name":"CVE-2025-67504","record":{"aliases":["GHSA-76gj-pmvx-jcc6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WBCE CMS","requires_auth":"none","summary":"Attackers can predict generated passwords due to insecure random number generation, leading to account takeover or privilege escalation in WBCE CMS.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wbce_cms","vendor":"wbce"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"},{"id":"CWE-331","name":"Insufficient Entropy"}],"description":"WBCE CMS is a content management system. Versions 1.6.4 and below use function GenerateRandomPassword() to create passwords using PHP's rand(). rand() is not cryptographically secure, which allows password sequences to be predicted or brute-forced. This can lead to user account compromise or privilege escalation if these passwords are used for new accounts or password resets. The vulnerability is fixed in version 1.6.5.","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":"WBCE CMS has Weak Random Number Generator in Password Generation Function","id":"CVE-2025-67504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Race condition in the Okta Java SDK","id":"CVE-2025-67505"},"packages":[],"prev":{"headline":"This CVE is a duplicate of another CVE.","id":"CVE-2025-67503"},"products":["WBCE_CMS"],"published":"2025-12-09","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-39796","kev_date_added":null,"published":"2023-11-10"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-46020","kev_date_added":null,"published":"2022-12-20"},{"cvss_score":9.8,"headline":"SQL Injection in wbce/wbce_cms","id":"CVE-2021-3817","kev_date_added":null,"published":"2021-12-09"},{"cvss_score":9.4,"headline":"WBCE CMS is Vulnerable to Time-Based Blind SQL Injection through groups[] Parameter","id":"CVE-2025-65950","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":8.7,"headline":"WBCE CMS 1.5.2 - Remote Code Execution (RCE) (Authenticated)","id":"CVE-2022-50936","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.7,"headline":"WBCE CMS 1.6.2 Remote Code Execution via Elfinder File Upload","id":"CVE-2024-58283","kev_date_added":null,"published":"2025-12-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-09","vendors":["WBCE"]},"summary":"Attackers can predict generated passwords due to insecure random number generation, leading to account takeover or privilege escalation in WBCE CMS.","url":"https://insights.sbomify.com/CVE-2025-67504/"}