LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24523: WordPress WP FullCalendar plugin <= 1.6 - Sensitive Data Exposure vulnerability

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Marcus (aka @msykes) WP FullCalendar wp-fullcalendar allows Retrieve Embedded Sensitive Data.This issue affects WP FullCalendar: from n/a through <= 1.6.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24523 affects the WordPress WP FullCalendar plugin through version 1.6. It may expose embedded sensitive system information to unauthenticated users. The published severity is medium, with confidentiality impact only. There is no provided evidence of active exploitation or inclusion in CISA KEV.

Executive priority

Treat as a medium-priority exposure issue. It is not currently supported as actively exploited, but unauthenticated network access means internet-facing WordPress sites should be checked promptly, especially where calendars may contain operational or sensitive information.

Technical view

The issue is classified as CWE-497: exposure of sensitive system information to an unauthorized control sphere. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, low confidentiality impact, no integrity or availability impact. Sources identify WP FullCalendar package wp-fullcalendar through <=1.6 as affected.

Likely exposure

Exposure is most likely on WordPress sites running the WP FullCalendar plugin version 1.6 or earlier. Public-facing WordPress deployments are more relevant because the CVSS vector indicates network access with no authentication required. Evidence does not identify specific configurations or data types exposed.

Exploitation context

The sources do not report active exploitation, public exploit code, or KEV listing. The vulnerability appears remotely reachable and unauthenticated based on CVSS, which raises scanning risk, but the known impact is limited to information exposure.

Researcher notes

Available public detail is limited. The record names the plugin, affected range, CWE, and CVSS, but does not describe the exact data exposed, vulnerable endpoint, patch version, or exploit conditions. Avoid assuming broader WordPress or FullCalendar library impact without vendor evidence.

Mitigation direction

  • Inventory WordPress sites for the WP FullCalendar plugin.
  • Confirm whether installed versions are 1.6 or earlier.
  • Check Patchstack and vendor guidance for a fixed release or official workaround.
  • If no fix is available, consider disabling or removing the plugin after change control.
  • Reduce public exposure of affected sites where business requirements allow.

Validation and detection

  • Review plugin inventory across production, staging, and legacy WordPress sites.
  • Verify the installed plugin version from administrative or asset records.
  • Check whether WP FullCalendar functionality is exposed to unauthenticated visitors.
  • Review web logs for unusual unauthenticated access to calendar-related resources.
  • Document affected instances and remediation decisions.
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 · low confidence lookup

CWE-497: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2026-24523 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-24523Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
Marcus (aka @msykes)WP FullCalendarwp-fullcalendar, 0unaffected
Weakness

CWE details

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

CWE-497 · source CWE mapping

Exposure of Sensitive System Information to an Unauthorized Control Sphere

Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.