Security readout for executives and security teams
Plain-English summary
CVE-2022-3852 affects the VR Calendar WordPress plugin through version 2.3.3. A malicious site or link could cause a logged-in administrator to unknowingly change plugin settings or modify/delete calendars. The issue depends on administrator interaction, but impact is high because site content and configuration can be changed.
Executive priority
Treat this as a high-priority WordPress plugin remediation if VR Calendar is present. It is not confirmed as actively exploited in the supplied sources, but administrator-assisted compromise could alter site data and settings.
Technical view
The vulnerability is cross-site request forgery caused by missing or incorrect nonce validation in several VR Calendar administrative functions. Sources describe unauthenticated attackers inducing an administrator action to perform state-changing operations, including calendar deletion, calendar modification, and plugin setting changes. The CVSS v3.1 score is 8.8.
Likely exposure
Exposure is limited to WordPress sites running VR Calendar versions up to and including 2.3.3. Sites without this plugin, or not using the affected versions, are not indicated as exposed by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Successful abuse requires a site administrator to be authenticated and tricked into taking an action such as clicking a link.
Researcher notes
The key weakness is CWE-352. Public references point to Wordfence, the WordPress plugin Trac source, and a changeset, but the prompt bundle does not name a specific fixed version. Avoid assuming patch details beyond the stated affected range.
Mitigation direction
- Inventory WordPress sites for VR Calendar or vr-calendar-sync.
- If running version 2.3.3 or older, prioritize upgrade or removal.
- Check vendor and WordPress plugin guidance for the confirmed fixed release.
- Restrict administrator browsing and access while remediation is pending.
- Review calendar and plugin settings for unexpected changes.
Validation and detection
- Confirm whether VR Calendar is installed on each WordPress site.
- Record the installed plugin version and compare against 2.3.3 or older.
- Review administrative functions for nonce validation on state-changing actions.
- Check site logs and change history for unexpected calendar or settings changes.
- Verify remediation against vendor or WordPress plugin release guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2022-3852 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a868226f-4ca1-4ec1-b55e-3029e3ed2d5b?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/vr-calendar-sync/tags/2.3.2/Admin/Classes/VRCalendarAdmin.class.php#L133CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2809350%40vr-calendar-sync&new=2809350%40vr-calendar-sync&sfp_email=&sfph_mail=CVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-3852CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.