# CVE-2025-10212: SiteAlert (Formerly WP Health) <= 1.9.8 - Missing Authorization to Unauthenticated Site Health Information Exposure

> Unauthenticated attackers can view sensitive site health information, including installed plugins and system versions, due to missing capability checks.

- **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:** 3 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gjm6-57g9-75x2

## What is CVE-2025-10212?

CVE-2025-10212 is a medium-severity missing authorization vulnerability in SiteAlert (Formerly WP Health), published on 3 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SiteAlert (Formerly WP Health) plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on multiple functions in all versions up to, and including, 1.9.8. This makes it possible for unauthenticated attackers to view the site health information, including a list of installed and outdated plugins, PHP and Database version, etc.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-10212 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10212 is a medium-severity missing authorization vulnerability in SiteAlert (Formerly WP Health), published on 3 Oct 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-10212 in the wild and no public exploit code.

Affected product: SiteAlert (Formerly WP Health). 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-10212/ (Markdown: https://insights.sbomify.com/CVE-2025-10212/index.md)
```

## Sources

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

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