LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45273: WordPress Stout Google Calendar Plugin <= 1.2.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Matt McKenny Stout Google Calendar plugin <= 1.2.3 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress Stout Google Calendar plugin up to version 1.2.3. An attacker could potentially trick a logged-in user into causing an unintended change. The published impact is limited to integrity, with no stated confidentiality or availability impact.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not reported as actively exploited, but it can affect site integrity if the vulnerable plugin is present and a user is tricked into interaction.

Technical view

CVE-2023-45273 is a CWE-352 Cross-Site Request Forgery vulnerability affecting Matt McKenny Stout Google Calendar plugin <= 1.2.3. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites that have Stout Google Calendar installed at version 1.2.3 or earlier. The sources do not identify affected configuration details beyond the plugin and version range.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not listed as KEV. Exploitation would require user interaction and appears aimed at unauthorized state-changing actions, not data theft or service disruption.

Researcher notes

Public details are sparse. The available sources identify CSRF, version range, CVSS, CWE, and Patchstack reference, but do not describe the vulnerable action, fixed version, or proof of exploitation. Avoid assuming impact beyond low integrity.

Mitigation direction

  • Inventory WordPress sites for Stout Google Calendar version 1.2.3 or earlier.
  • Check vendor or WordPress plugin guidance for a fixed release or official workaround.
  • Update the plugin if a fixed version is available from a trusted source.
  • Disable or remove the plugin where it is not business-critical.
  • Limit administrative browsing while logged in until remediation is complete.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the installed plugin version and compare it with the <= 1.2.3 affected range.
  • Review vendor or plugin repository notes for remediation status.
  • Check whether administrative workflows depend on this plugin before disabling it.
  • Verify remediation by confirming the vulnerable version is no longer active.
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-2023-45273 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
4.3 (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:N

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-45273Attack 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:N

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
Matt McKennyStout Google Calendarstout-google-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.