# CVE-2022-25599: WordPress Spiffy Calendar plugin <= 4.9.0 - Event deletion via Cross-Site Request Forgery (CSRF) vulnerability

> Attackers can trick authenticated users into deleting calendar events via CSRF in the Spiffy Calendar WordPress plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **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:** 21 Feb 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-w7h5-gm2r-5xj4

## What is CVE-2022-25599?

CVE-2022-25599 is a medium-severity vulnerability in Spiffy Calendar (WordPress plugin), published on 21 Feb 2022. 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

Cross-Site Request Forgery (CSRF) vulnerability leading to event deletion was discovered in Spiffy Calendar WordPress plugin (versions <= 4.9.0).

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

## Which versions are affected by CVE-2022-25599?

It affects 1 product.


Products: Spiffyplugins Spiffy Calendar.

## How do I fix CVE-2022-25599?

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

## Is CVE-2022-25599 being exploited?

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

## Other vulnerabilities in Spiffy Calendar (WordPress plugin)

- [CVE-2022-46859](https://insights.sbomify.com/CVE-2022-46859/): WordPress Spiffy Calendar Plugin <= 4.9.1 is vulnerable to SQL Injection (high 8.5)
- [CVE-2024-38692](https://insights.sbomify.com/CVE-2024-38692/): WordPress spiffy-calendar plugin <= 4.9.11 - SQL Injection vulnerability (high 7.6)
- [CVE-2024-45458](https://insights.sbomify.com/CVE-2024-45458/): WordPress Spiffy Calendar plugin <= 4.9.13 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-45457](https://insights.sbomify.com/CVE-2024-45457/): WordPress Spiffy Calendar plugin <= 4.9.13 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2023-49745](https://insights.sbomify.com/CVE-2023-49745/): WordPress Spiffy Calendar Plugin <= 4.9.5 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25599 and fix it if it is affected.

What it is: CVE-2022-25599 is a medium-severity vulnerability in Spiffy Calendar (WordPress plugin), published on 21 Feb 2022. 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-2022-25599 in the wild and no public exploit code.

Affected product: Spiffy Calendar (WordPress plugin). 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-2022-25599/ (Markdown: https://insights.sbomify.com/CVE-2022-25599/index.md)
```

## Sources

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

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