{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12363 is a high-severity vulnerability in n/a, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-12363 and fix it if it is affected.\n\nWhat it is: CVE-2019-12363 is a high-severity vulnerability in n/a, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-12363 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-12363/ (Markdown: https://insights.sbomify.com/CVE-2019-12363/index.md)","id":"CVE-2019-12363","markdown":"https://insights.sbomify.com/CVE-2019-12363/index.md","name":"CVE-2019-12363","record":{"aliases":["GHSA-cp4x-gprf-24pm"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MyBB 2FA plugin","requires_auth":"none","summary":"An attacker can force a user to disable two-factor authentication via a forged request, lowering account security.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mybb-2fa","vendor":"mybb-2fa_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An CSRF issue was discovered in the JN-Jones MyBB-2FA plugin through 2014-11-05 for MyBB. An attacker can forge a request to an installed mybb2fa plugin to control its state via usercp.php?action=mybb2fa\u0026do=deactivate (or usercp.php?action=mybb2fa\u0026do=activate). A deactivate operation lowers the security of the targeted account by disabling two factor authentication.","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":"Cross-site request forgery in n/a","id":"CVE-2019-12363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-12365"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-12362"},"products":["n/a"],"published":"2019-07-11","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can force a user to disable two-factor authentication via a forged request, lowering account security.","url":"https://insights.sbomify.com/CVE-2019-12363/"}