LiveActive security incident?Get immediate response
CVE Record

CVE-2022-33177: WordPress Booking Calendar plugin <= 9.2.1 - Cross-Site Request Forgery (CSRF) vulnerabiulity

Cross-Site Request Forgery (CSRF) vulnerability in WPdevelop/Oplugins Booking Calendar plugin <= 9.2.1 at WordPress leading to Translations Update.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-33177 is a CSRF issue in the WordPress Booking Calendar plugin. A user could be tricked into causing an unintended translations update on a site running version 9.2.1 or earlier. The reported impact is limited integrity and availability, with no confidentiality impact in the supplied scoring.

Executive priority

Treat this as a moderate WordPress plugin maintenance risk. It is not listed as KEV and has limited scored impact, but internet-facing WordPress sites should still be updated because CSRF issues can cause unintended administrative actions.

Technical view

The issue is CWE-352 in WPdevelop/Oplugins Booking Calendar for WordPress versions <= 9.2.1. The CVSS 3.1 score is 5.4, with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, low integrity impact, and low availability impact.

Likely exposure

Exposure is limited to WordPress sites using Booking Calendar version 9.2.1 or earlier. The source bundle does not identify other affected products, CPEs, hosting platforms, or configuration-specific prerequisites beyond the plugin version.

Exploitation context

The CVE describes CSRF leading to translations update and requires user interaction. The bundle does not cite active exploitation, and KEV status is false. No public exploit status is supported by the provided sources.

Researcher notes

Evidence is limited to the CVE metadata and referenced vendor/advisory pages. The bundle identifies affected versions and impact category but does not include nonce details, endpoint names, proof of concept, or a confirmed fixed version.

Mitigation direction

  • Inventory WordPress sites for the Booking Calendar plugin and installed version.
  • Prioritize sites running Booking Calendar 9.2.1 or earlier.
  • Check WPdevelop/Oplugins or WordPress plugin guidance for the fixed release.
  • Upgrade according to vendor guidance when a fixed version is available.
  • Reduce unnecessary privileged WordPress sessions until remediation is complete.

Validation and detection

  • Confirm whether Booking Calendar is installed on each WordPress site.
  • Record the plugin version and compare it with <= 9.2.1.
  • Review plugin vendor release notes for remediation details.
  • Verify the site runs a vendor-supported version after updating.
  • Document affected sites, remediation date, and remaining exceptions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-33177 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-33177Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WPdevelop/OpluginsBooking Calendar (WordPress plugin)<= 9.2.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.