# CVE-2005-0905: Information disclosure in n/a

> Remote attackers can obtain sensitive data from the search bar via the m2_search_text property in Maxthon browser.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q4px-9qgf-fhgq

## What is CVE-2005-0905?

CVE-2005-0905 is a low-severity vulnerability in n/a, published on 29 Mar 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Maxthon 1.2.0 allows remote malicious web sites to obtain potentially sensitive data from the search bar via the m2_search_text property.

## Which versions are affected by CVE-2005-0905?

It affects 1 product.


Products: Maxthon Maxthon.

## How do I fix CVE-2005-0905?

No fix has been published for CVE-2005-0905 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-0905 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0905 exists.

Public exploit code:

- Maxthon Web Browser 1.2 - Search Bar Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-1090](https://insights.sbomify.com/CVE-2005-1090/): Path traversal in n/a (medium 6.4)
- [CVE-2006-6985](https://insights.sbomify.com/CVE-2006-6985/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0905 and fix it if it is affected.

What it is: CVE-2005-0905 is a low-severity vulnerability in n/a, published on 29 Mar 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0905 exists.

Affected product: n/a. 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-2005-0905/ (Markdown: https://insights.sbomify.com/CVE-2005-0905/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-0905
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-0905
- OSV: https://osv.dev/vulnerability/CVE-2005-0905

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-0905/
Summaries are generated and may contain mistakes; the official description above is the record.