LiveActive security incident?Get immediate response
CVE Record

CVE-2022-47427: WordPress My Calendar Plugin <= 3.3.24.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Joseph C Dolson My Calendar plugin <= 3.3.24.1 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress My Calendar plugin. An attacker could trick an authenticated user into performing unintended plugin-related actions, potentially affecting site content or availability. The source bundle does not show active exploitation.

Executive priority

Treat as a normal-priority remediation item for WordPress estates using this plugin. It is not KEV-listed in the provided data, but it can affect integrity or availability if a privileged user is tricked.

Technical view

CVE-2022-47427 is a CWE-352 Cross-Site Request Forgery vulnerability affecting Joseph C Dolson My Calendar plugin versions <= 3.3.24.1. CVSS 3.1 is 5.4, with network attack vector, low complexity, no attacker privileges, required user interaction, and limited integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the My Calendar plugin installed at version 3.3.24.1 or earlier. Risk is higher where privileged WordPress users stay authenticated while browsing untrusted content.

Exploitation context

The CVSS vector requires user interaction and shows no confidentiality impact. The bundle marks KEV as false, and the cited sources do not provide evidence of known exploited status or public exploit maturity.

Researcher notes

The public data identifies the vulnerability class, affected plugin threshold, CVSS vector, and CWE. It does not provide exploit details, a specific fixed version, or confirmed in-the-wild exploitation. Avoid assuming broader WordPress impact beyond this plugin.

Mitigation direction

  • Inventory WordPress sites for the My Calendar plugin.
  • Upgrade the plugin following vendor or Patchstack guidance if a fixed release is available.
  • Disable or remove the plugin where upgrade status cannot be confirmed.
  • Limit privileged WordPress admin sessions to trusted workflows.
  • Monitor vendor advisories for exact remediation guidance.

Validation and detection

  • Confirm whether My Calendar is installed on each WordPress site.
  • Verify no installed version is 3.3.24.1 or earlier.
  • Review Patchstack or vendor guidance for fixed-version details.
  • Test calendar functionality after update, disablement, or removal.
  • Review admin activity for unexpected calendar-related changes.
Prepared
Confidence
medium
Sources
3

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-47427 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
2Source 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-47427Attack 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
Joseph C DolsonMy Calendarmy-calendar, n/aunaffected
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.