{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9488 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9488 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9488 is a critical authentication bypass vulnerability in advancedcoding Comments – wpDiscuz, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9488 and fix it if it is affected.\n\nWhat it is: CVE-2024-9488 is a critical authentication bypass vulnerability in advancedcoding Comments – wpDiscuz, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-9488 in the wild and no public exploit code.\n\nAffected product: advancedcoding Comments – wpDiscuz. 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-2024-9488/ (Markdown: https://insights.sbomify.com/CVE-2024-9488/index.md)","id":"CVE-2024-9488","markdown":"https://insights.sbomify.com/CVE-2024-9488/index.md","name":"CVE-2024-9488","record":{"aliases":["GHSA-h9x6-qcr3-mf95"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can log in as any existing user, including administrators, via the WordPress.com OAuth provider if they know the user's email.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wpdiscuz","vendor":"gvectors"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"The Comments – wpDiscuz plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 7.6.24. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Comments – wpDiscuz \u003c= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider","id":"CVE-2024-9488","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Autodesk AutoCAD DWG File Parsing Memory Corruption Code Execution Vulnerability","id":"CVE-2024-9489"},"packages":[],"prev":{"headline":"Auth bypass in Enterprise Server","id":"CVE-2024-9487"},"products":["Comments – wpDiscuz"],"published":"2024-10-25","related":[{"cvss_score":10,"headline":"File upload in n/a","id":"CVE-2020-24186","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-13640","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":9.2,"headline":"wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions()","id":"CVE-2026-22193","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.8,"headline":"Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage","id":"CVE-2026-22192","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.7,"headline":"wpDiscuz before 7.6.47 - Unauthenticated Email Notification Flood via wpdCheckNotificationType","id":"CVE-2026-22182","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.7,"headline":"Voltronic Power SNMP Web Pro 1.1 Path Traversal via upload.cgi","id":"CVE-2026-22199","kev_date_added":null,"published":"2026-03-13"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["advancedcoding"]},"summary":"Unauthenticated attackers can log in as any existing user, including administrators, via the WordPress.com OAuth provider if they know the user's email.","url":"https://insights.sbomify.com/CVE-2024-9488/"}