# CVE-2025-4769: CBEWIN Anytxt Searcher ATService.exe uncontrolled search path

> Local attackers can exploit uncontrolled search paths in Anytxt Searcher to execute arbitrary code via DLL hijacking.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-mjcv-5hrg-8v8x

## What is CVE-2025-4769?

CVE-2025-4769 is a high-severity path traversal vulnerability in CBEWIN Anytxt Searcher, published on 16 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in CBEWIN Anytxt Searcher 1.3.1128.0. This vulnerability affects unknown code of the file ATService.exe. The manipulation leads to uncontrolled search path. The attack needs to be approached locally. The complexity of an attack is rather high. The exploitation appears to be difficult.

Weakness: CWE-427 (Uncontrolled Search Path Element), CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2025-4769?


## How do I fix CVE-2025-4769?

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

## Is CVE-2025-4769 being exploited?

There is no known exploitation of CVE-2025-4769 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4769 and fix it if it is affected.

What it is: CVE-2025-4769 is a high-severity path traversal vulnerability in CBEWIN Anytxt Searcher, published on 16 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4769 in the wild and no public exploit code.

Affected product: CBEWIN Anytxt Searcher. 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-4769/ (Markdown: https://insights.sbomify.com/CVE-2025-4769/index.md)
```

## Sources

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

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