# CVE-2026-18480: SureCart < 4.6.3 - Subscriber+ Administrator Account Takeover

> Subscribers can take over administrator accounts by modifying email addresses due to missing authorization checks in SureCart.

- **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:** 6 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-4jgg-5r84-r28r

## What is CVE-2026-18480?

CVE-2026-18480 is a high-severity missing authorization vulnerability in Unknown SureCart, published on 6 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SureCart  WordPress plugin before 4.6.3 does not ensure that the account affected by a customer update is the same account its permission check authorised, allowing users with a subscriber-level account to change another user's email address, including an administrator's, and take over that account via a password reset. It further allows an attacker-controlled customer record to be associated with an arbitrary user, and discloses customer identifiers and email addresses to any authenticated user, which together make the takeover reachable from a subscriber-level account alone.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-18480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18480 is a high-severity missing authorization vulnerability in Unknown SureCart, published on 6 Sep 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-18480 in the wild and no public exploit code.

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

## Sources

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

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