# CVE-2022-0212: SpiderCalendar <= 1.5.65 - Reflected Cross-Site Scripting

> Attackers can inject malicious scripts via the callback parameter in SpiderCalendar, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 14 Feb 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vcj8-8g5f-vhr9

## What is CVE-2022-0212?

CVE-2022-0212 is a medium-severity cross-site scripting vulnerability in Unknown SpiderCalendar, published on 14 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

The SpiderCalendar WordPress plugin through 1.5.65 does not sanitise and escape the callback parameter before outputting it back in the page via the window AJAX action (available to both unauthenticated and authenticated users), leading to a Reflected Cross-Site Scripting issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: 10web Spidercalendar.

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

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

## Is CVE-2022-0212 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0212 exists.

Public exploit code:

- WordPress Spider Calendar <=1.5.65 - Cross-Site Scripting (nuclei): http/cves/2022/CVE-2022-0212.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0212 is a medium-severity cross-site scripting vulnerability in Unknown SpiderCalendar, published on 14 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0212 exists.

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

## Sources

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

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