# CVE-2026-92410: Sign-up Sheets < 2.4.0 - Arbitrary Sign-up Deletion via CSRF

> Attackers can delete sign-up records via forged requests in logged-in user sessions due to missing CSRF validation in the Sign-up Sheets plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 20 Sep 2026
- **Also known as:** GHSA-9547-95qm-hm4c

## What is CVE-2026-92410?

CVE-2026-92410 is a medium-severity vulnerability in Unknown Sign-up Sheets, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Sign-up Sheets WordPress plugin before 2.4.0 does not properly validate the CSRF nonce that protects its sign-up deletion action, allowing attackers to delete sign-up records via a forged request handled in the session of a logged-in user with the required capability.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-92410 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92410 is a medium-severity vulnerability in Unknown Sign-up Sheets, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92410 in the wild and no public exploit code.

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

## Sources

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

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