{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49952 exists.","fix":"No fix has been published for CVE-2026-49952 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49952 is a critical authentication bypass vulnerability in Discuz! X5.0, published on 15 Jun 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-49952 and fix it if it is affected.\n\nWhat it is: CVE-2026-49952 is a critical authentication bypass vulnerability in Discuz! X5.0, published on 15 Jun 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-49952 exists.\n\nAffected product: Discuz! X5.0. 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-49952/ (Markdown: https://insights.sbomify.com/CVE-2026-49952/index.md)","id":"CVE-2026-49952","markdown":"https://insights.sbomify.com/CVE-2026-49952/index.md","name":"CVE-2026-49952","record":{"aliases":["GHSA-mx47-h32c-x878"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Discuz! forum software","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication to access database backup and restore functions, potentially modifying data or impersonating users.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-323","name":"Reusing a Nonce, Key Pair in Encryption"}],"description":"Discuz! X5.0 releases 20260320 through 20260501 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to gain unauthorized access to database backup and restore functionality by exploiting a shared cryptographic key between UCenter integration and the database backup API exposed by dbbak.php. Attackers can inject a crafted payload through the username parameter during login to abuse the encryption oracle in logging_ctl::logging_more(), obtain a legitimately signed token, and use it to bypass authorization for database export and import operations, with the additional ability to trigger a race condition to impersonate arbitrary users.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2026-06-17","github_poc":2,"max_poc_stars":3,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-06-17T09:04:23Z","kind":"github_poc","ref":"https://github.com/passwa11/CVE-2026-49952","stars":3,"title":"Chaining Security Bugs in Discuz! X5.0: from Race Condition to Pre-Auth RCE"},{"date":"2026-07-24T18:08:35Z","kind":"github_poc","ref":"https://github.com/CerberusMrXi/Discuz-X5.0-Authentication-Bypass-Exploit-Framework","stars":1,"title":"Discuz! X5.0 Authentication Bypass Exploit Framework (CVE-2026-49952) - Critical vulnerability allowing unauthenticated database backup access via UC_KEY encryption oracle token reuse. CVSS 9.1. Full-featured tool with version detection, multi-payload attacks, interactive shell, and automated exploitation. Authorized testing only."},{"date":"2026-07-07","kind":"exploitdb","ref":"52621","stars":null,"title":"Discuz! X5.0 - Authentication Bypass"},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-49952.yaml","stars":null,"title":"Discuz! X5.0 - Authentication Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Discuz! X5.0 Authentication Bypass via dbbak.php Encryption Oracle","id":"CVE-2026-49952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Discuz! X5.0 CAPTCHA Bypass via Predictable Character Set","id":"CVE-2026-49953"},"packages":[],"prev":{"headline":"Xorbits Xoscar 0.11.2 Unauthenticated Deserialization RCE via Actor Pool","id":"CVE-2026-49950"},"products":["Discuz! X5.0"],"published":"2026-06-15","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["Discuz!"]},"summary":"Unauthenticated attackers can bypass authentication to access database backup and restore functions, potentially modifying data or impersonating users.","url":"https://insights.sbomify.com/CVE-2026-49952/"}