# CVE-2025-48941: MyBB may disclosure unviewable threads' titles in searches > Attackers can determine the existence of hidden threads via search response differences, leaking metadata about unapproved or deleted content. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 2 Jun 2025 - **Updated:** 2 Jun 2025 - **Also known as:** GHSA-f847-57xc-ffwr ## What is CVE-2025-48941? CVE-2025-48941 is a medium-severity vulnerability in Mybb Mybb, published on 2 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description MyBB is free and open source forum software. Prior to version 1.8.39, the search component does not validate permissions correctly, which allows attackers to determine the existence of hidden (draft, unapproved, or soft-deleted) threads containing specified text in the title. The visibility state (`mybb_threads.visible` integer column) of threads is not validated in internal search queries, whose result is used to output a general success or failure of the search. While MyBB validates permissions when displaying the final search results, a search operation that internally produces at least one result outputs a redirect response (as a HTTP redirect, or a success message page with delayed redirect, depending on configuration). On the other hand, a search operation that internally produces no results outputs a corresponding message in the response without a redirect. This allows a user to determine whether threads matching title search parameters exist, including draft threads (`visible` with a value of `-2`), soft-deleted threads (`visible` with a value of `-1`), and unapproved threads (`visible` with a value of `0`); in addition to displaying generally visible threads (`visible` with a value of `1`). This vulnerability does not affect other layers of permissions. In order to exploit the vulnerability, the user must have access to the search functionality, and general access to forums containing the thread(s). The vulnerability does not expose the message content of posts. MyBB 1.8.39 resolves this issue. Weakness: CWE-1230 (Exposure of Sensitive Information Through Metadata) ## Which versions are affected by CVE-2025-48941? It affects 1 product. Products: Mybb Mybb. ## How do I fix CVE-2025-48941? No fix has been published for CVE-2025-48941 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-48941 being exploited? There is no known exploitation of CVE-2025-48941 in the wild and no public exploit code. ## Other vulnerabilities in Mybb Mybb - [CVE-2011-10018](https://insights.sbomify.com/CVE-2011-10018/): myBB 1.6.4 Backdoor Arbitrary Command Execution (critical 10.0) - [CVE-2015-2786](https://insights.sbomify.com/CVE-2015-2786/): Information disclosure in n/a (critical 10.0) - [CVE-2011-5133](https://insights.sbomify.com/CVE-2011-5133/): Cross-site scripting in n/a (critical 10.0) - [CVE-2006-0218](https://insights.sbomify.com/CVE-2006-0218/): SQL injection in n/a (critical 10.0) - [CVE-2020-22612](https://insights.sbomify.com/CVE-2020-22612/): Code injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-48941 and fix it if it is affected. What it is: CVE-2025-48941 is a medium-severity vulnerability in Mybb Mybb, published on 2 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-48941 in the wild and no public exploit code. Affected product: Mybb Mybb. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-48941/ (Markdown: https://insights.sbomify.com/CVE-2025-48941/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48941 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48941 - OSV: https://osv.dev/vulnerability/CVE-2025-48941 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-48941/ Summaries are generated and may contain mistakes; the official description above is the record.