{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47245 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47245 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47245 is a medium-severity vulnerability in mybb, published on 18 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-47245 and fix it if it is affected.\n\nWhat it is: CVE-2026-47245 is a medium-severity vulnerability in mybb, published on 18 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-47245 in the wild and no public exploit code.\n\nAffected product: mybb. 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-47245/ (Markdown: https://insights.sbomify.com/CVE-2026-47245/index.md)","id":"CVE-2026-47245","markdown":"https://insights.sbomify.com/CVE-2026-47245/index.md","name":"CVE-2026-47245","record":{"aliases":["GHSA-w8gm-j57p-jqpc"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-252","name":"Unchecked Return Value"}],"description":"MyBB is free and open source forum software. Prior to 1.8.40, the User CP Buddy/Ignore List component does not validate reciprocal buddy-list updates correctly. The usercp.php?action=do_editlists delete handler removes the selected entry from the acting user's list and then updates mybb_users.buddylist for the target account. The reciprocal update searches for the deleted target UID instead of the acting user's UID and uses the unchecked array_search() return value as an array key. A false result can be converted to index 0, removing the target account's first stored buddy while leaving the actual reciprocal entry unchanged. The uniquely identifying implementation details include false converted to index 0. This issue is fixed in version 1.8.40.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MyBB: Buddy list corruption","id":"CVE-2026-47245","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"libheif Vulnerable to Heap Information Disclosure via Grid Image Gap + Uninitialized Pixel Plane Allocation","id":"CVE-2026-47247"},"packages":[],"prev":{"headline":"Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced","id":"CVE-2026-47244"},"products":["mybb"],"published":"2026-08-18","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["mybb"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-47245/"}