# CVE-2026-94258: SMS Alert 3.6.4 - 4.0.0 - Admin+ Network User Billing Phone Disclosure via Bulk User Actions

> An administrator on one site in a multisite network can disclose billing phone numbers of users from other sites due to missing authorization checks.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-v3cq-2qmr-2qf3

## What is CVE-2026-94258?

CVE-2026-94258 is a low-severity vulnerability in Unknown SMS Alert, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The SMS Alert  WordPress plugin before 4.0.1 does not check that the acting administrator is allowed to manage the selected users before returning their stored billing phone numbers, allowing an administrator of one site on a multisite network to disclose the phone numbers of users who belong to other sites on that network.
This affects multisite only, and requires the SMS Alert  WordPress plugin before 4.0.1's gateway credentials to be stored on the acting administrator's own site.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-94258?


## How do I fix CVE-2026-94258?

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

## Is CVE-2026-94258 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94258 and fix it if it is affected.

What it is: CVE-2026-94258 is a low-severity vulnerability in Unknown SMS Alert, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94258 in the wild and no public exploit code.

Affected product: Unknown SMS Alert. 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-2026-94258/ (Markdown: https://insights.sbomify.com/CVE-2026-94258/index.md)
```

## Sources

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

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