# CVE-2022-46859: WordPress Spiffy Calendar Plugin <= 4.9.1 is vulnerable to SQL Injection

> Attackers can execute arbitrary SQL commands via the Spiffy Calendar plugin, potentially reading or modifying database content.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **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:** 3 Nov 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8g6j-479w-669q

## What is CVE-2022-46859?

CVE-2022-46859 is a high-severity SQL injection vulnerability in Spiffy Calendar, published on 3 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Spiffy Plugins Spiffy Calendar spiffy-calendar allows SQL Injection.This issue affects Spiffy Calendar: from n/a through 4.9.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Spiffyplugins Spiffy Calendar.

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

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

## Is CVE-2022-46859 being exploited?

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

## Other vulnerabilities in Spiffy Calendar

- [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)
- [CVE-2022-29434](https://insights.sbomify.com/CVE-2022-29434/): WordPress Spiffy Calendar plugin <= 4.9.0 - Edit/Delete event via IDOR vulnerability (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46859 is a high-severity SQL injection vulnerability in Spiffy Calendar, published on 3 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46859 in the wild and no public exploit code.

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

## Sources

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

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