# CVE-2026-93548: FooSales < 1.43.3 - Subscriber+ Privilege Escalation via User Impersonation

> Authenticated users can impersonate administrators to take over accounts due to missing authorization checks in the FooSales plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-84fg-vq45-2j4v

## What is CVE-2026-93548?

CVE-2026-93548 is a high-severity vulnerability in Unknown FooSales, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The FooSales  WordPress plugin before 1.43.3 does not verify that an authenticated caller is entitled to act as the user a request names, allowing any authenticated user to have the FooSales  WordPress plugin before 1.43.3 act as an arbitrary other user, including an administrator, resulting in that user's account details being exposed and their account being taken over.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-93548 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93548 is a high-severity vulnerability in Unknown FooSales, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93548 in the wild and no public exploit code.

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

## Sources

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

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