# CVE-2026-84907: Eventin < 4.1.24 - Unauthenticated Order and Attendee Status Reset via Payment REST Endpoint

> Unauthenticated attackers can reset paid Eventin orders to pending status via a REST endpoint when offline payments are enabled, invalidating tickets.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-8p9w-4xhq-w374

## What is CVE-2026-84907?

CVE-2026-84907 is a low-severity missing authorization vulnerability in Unknown Eventin, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Eventin  WordPress plugin before 4.1.24 does not properly authorise order finalisation when its offline (local) payment method is enabled, relying on a nonce that is exposed to unauthenticated visitors and never checking that the caller owns the order, allowing unauthenticated attackers to reset any existing order and its attendees to a pending state and thereby invalidate paid tickets.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-84907 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84907 is a low-severity missing authorization vulnerability in Unknown Eventin, published on 16 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-84907 in the wild and no public exploit code.

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

## Sources

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

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