# CVE-2026-3174: Event Tickets and Registration <= 5.27.4 - Missing Authorization to Unauthenticated Stripe Credentials Update

> Unauthenticated attackers can overwrite Stripe credentials in the Event Tickets plugin, diverting payments to their own accounts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 8 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-5qhm-7c6f-ffj5

## What is CVE-2026-3174?

CVE-2026-3174 is a high-severity missing authorization vulnerability in stellarwp Event Tickets and Registration, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Event Tickets and Registration plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the Stripe OAuth return endpoint in all versions up to, and including, 5.27.4. This makes it possible for unauthenticated attackers to overwrite the site's Stripe merchant credentials (access tokens, publishable keys, and account ID), diverting all subsequent payment processing to the attacker's Stripe account.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-3174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3174 is a high-severity missing authorization vulnerability in stellarwp Event Tickets and Registration, published on 8 Sep 2026. 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-2026-3174 in the wild and no public exploit code.

Affected product: stellarwp Event Tickets and Registration. 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-3174/ (Markdown: https://insights.sbomify.com/CVE-2026-3174/index.md)
```

## Sources

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

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