# CVE-2024-12902: Global Wisdom Software ANCHOR - Undocumented Privileged Account

> Attackers can remotely log in to the ANCHOR virtual machine using default high-privilege service account passwords, leading to full system compromise.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2024
- **Updated:** 24 Dec 2024
- **Also known as:** GHSA-gxjr-h8qg-gpq4

## What is CVE-2024-12902?

CVE-2024-12902 is a high-severity vulnerability in Global Wisdom Software ANCHOR, published on 23 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ANCHOR from Global Wisdom Software is an integrated product running on a Windows virtual machine. The underlying Windows OS of the product contains high-privilege service accounts. If these accounts use default passwords, attackers could remotely log in to the virtual machine using the default credentials.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2024-12902?


## How do I fix CVE-2024-12902?

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

## Is CVE-2024-12902 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12902 and fix it if it is affected.

What it is: CVE-2024-12902 is a high-severity vulnerability in Global Wisdom Software ANCHOR, published on 23 Dec 2024. 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-2024-12902 in the wild and no public exploit code.

Affected product: Global Wisdom Software ANCHOR. 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-2024-12902/ (Markdown: https://insights.sbomify.com/CVE-2024-12902/index.md)
```

## Sources

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

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