# CVE-2022-3891: WP FullCalendar < 1.5 - Unauthenticated Arbitrary Post Access

> Unauthenticated attackers can access content of arbitrary posts, including drafts and private ones, via an AJAX action in the WP FullCalendar plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2023
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-ghxw-rgqv-5cp6

## What is CVE-2022-3891?

CVE-2022-3891 is a medium-severity missing authorization vulnerability in Unknown WP FullCalendar, published on 13 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP FullCalendar WordPress plugin before 1.5 does not ensure that the post retrieved via an AJAX action is public and can be accessed by the user making the request, allowing unauthenticated attackers to get the content of arbitrary posts, including draft/private as well as password-protected ones.

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

It affects 1 product.


Products: Pixelite Wp Fullcalendar.

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

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

## Is CVE-2022-3891 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3891 is a medium-severity missing authorization vulnerability in Unknown WP FullCalendar, published on 13 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3891 exists.

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

## Sources

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

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