CVE-2022-36399 WordPress Booked Plugin < 2.4.4 is vulnerable to Sensitive Data Exposure
Medium 5.3
Published
Updated
Check this codebase for CVE-2022-36399 and fix it if it is affected.
What it is: CVE-2022-36399 is a medium-severity vulnerability in BoxyStudio Booked - Appointment Booking for WordPress | Calendars, published on 28 Dec 2023.
Exploitation: There is no known exploitation of CVE-2022-36399 in the wild and no public exploit code.
Affected product: BoxyStudio Booked - Appointment Booking for WordPress | Calendars. 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-36399/ (Markdown: https://insights.sbomify.com/CVE-2022-36399/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2022-36399?
CVE-2022-36399 is a medium-severity vulnerability in BoxyStudio Booked - Appointment Booking for WordPress | Calendars, published on 28 Dec 2023.
Official description
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in BoxyStudio Booked - Appointment Booking for WordPress | Calendars.This issue affects Booked - Appointment Booking for WordPress | Calendars: from n/a before 2.4.4.
Weakness: CWE-200
Which versions are affected by CVE-2022-36399?
It affects 1 product.
Products include Boxystudio Booked.
How do I fix CVE-2022-36399?
No fix has been published for CVE-2022-36399 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-36399 being exploited?
There is no known exploitation of CVE-2022-36399 in the wild and no public exploit code.
Sources
Also known as GHSA-54wr-xmjg-j9mj.