{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13820 exists.","fix":"No fix has been published for CVE-2025-13820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-13820 is a medium-severity authentication bypass vulnerability in Unknown Comments, published on 1 Jan 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-2025-13820 and fix it if it is affected.\n\nWhat it is: CVE-2025-13820 is a medium-severity authentication bypass vulnerability in Unknown Comments, published on 1 Jan 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-2025-13820 exists.\n\nAffected product: Unknown Comments. 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-13820/ (Markdown: https://insights.sbomify.com/CVE-2025-13820/index.md)","id":"CVE-2025-13820","markdown":"https://insights.sbomify.com/CVE-2025-13820/index.md","name":"CVE-2025-13820","record":{"aliases":["GHSA-77g2-3gj2-8h4q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can take over accounts of users without Disqus profiles by exploiting improper identity validation in the wpDiscuz plugin.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Comments  WordPress plugin before 7.6.40 does not properly validate user's identity when using the disqus.com provider, allowing an attacker to log in to any user (when knowing their email address) when such user does not have an account on disqus.com yet.","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":"Comments – wpDiscuz \u003c 7.6.40 - Unauthenticated Account Takeover","id":"CVE-2025-13820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"User profile update exposes password hash and MFA secrets","id":"CVE-2025-13821"},"packages":[],"prev":{"headline":"Open redirect in web server of MiR robots and MiR fleet","id":"CVE-2025-13819"},"products":["Comments"],"published":"2026-01-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-05","vendors":["Unknown"]},"summary":"An attacker can take over accounts of users without Disqus profiles by exploiting improper identity validation in the wpDiscuz plugin.","url":"https://insights.sbomify.com/CVE-2025-13820/"}