# CVE-2022-4115: Editorial Calendar < 3.8.3 - Contributor+ Stored XSS

> Contributors can inject scripts into the Editorial Calendar plugin settings, leading to stored XSS attacks against higher-privileged users.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-c3jj-9wrg-44g9

## What is CVE-2022-4115?

CVE-2022-4115 is a medium-severity cross-site scripting vulnerability in Unknown Editorial Calendar, published on 27 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Editorial Calendar WordPress plugin before 3.8.3 does not sanitise and escape its settings, allowing users with roles as low as contributor to inject arbitrary web scripts in the plugin admin panel, enabling a Stored Cross-Site Scripting vulnerability targeting higher privileged users.

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

It affects 1 product.


Products: Editorial Calendar Project Editorial Calendar.

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

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

## Is CVE-2022-4115 being exploited?

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

## Other vulnerabilities in Unknown Editorial Calendar

- [CVE-2013-10023](https://insights.sbomify.com/CVE-2013-10023/): Editorial Calendar Plugin edcal.php edcal_filter_where sql injection (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4115 is a medium-severity cross-site scripting vulnerability in Unknown Editorial Calendar, published on 27 Jun 2023. Any signed-in user can exploit it over the network, 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-4115 exists.

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

## Sources

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

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